Question

Pick three questions from the following list and write a thorough 3-5 paragraph response.

1. Explain the primary role and responsibilities of business analysts/system analysts.

2. Describe the need for Business Process Management. What is an AS IS model?

3. Describe the origins of SDLC and how it came to prominence.

4. Explain two reasons why SDLC is falling out of favor.

5. Describe advantages of using Agile methods like Scrum.

6. What are the keys for successful SDLC projects?

7. How can Agile overcome the problems of the SDLC?

8. How do information systems support business processes?

9. Comment on you own experiences with business process improvement and systems development projects you have seen at your employer.

Answer 1

****This requires some effort so please drop a like if you are satisfied with the solution****

1. The roles and responsibilities of Business/System Analysts:

The primary responsibility of business/system analyst is to identify the requirements of the work and the capability of effort involved and analyse whether if it is effective to take up the project or not.Improve current systems by identifying outdated technologies and systems and suggest newer and stable technologies that make the development and maintainence easier.

Identifying problems and providing effective and easy to implement solution that are both budget friendly and profitable at the same time, constant monitoring of project status whether the project is moving as per schedule or anything is lagging behind and following up employees to make sure that the project or work is on schedule.

Managing deliverables on time and checking the quality of the work that is to be delivered to the client, maintaining the trust and confidence of the user as well as client by ensuring work quality and on time delivery. Making reports by collection technical information as well as non-technical information and providing insights based on the reports for further growth.

5. Advantages of Agile method Scrum:

• Provides better understanding of the project as the whole project need not be completed on one go and only some part of project called viable product has to be developed.
• The project will be flexible as changing requirements can be easily implemented and added to the current product.
• Better interaction between the client, developers, testing, and end users which results in a better product.
• Constant monitoring of project status and continuous feedback which helps in identifying threats and problems that may arise during the process of project development, this is achieved in Agile methodology by daily stand up meetings called SCRUM meetings.
• The project development is divided into sections of time called sprints which enables better understanding in the process of development and testing and also facilitates innovation of newer features into the project.

7.

In a traditional software development life cycle which follows waterfall model has a number of disadvantages and inconsistencies when compared to Agile model of SDLC. Some of these inconsistencies are:

• In traditional model the process is a one way street, if the project passes one state it is not possible to step back if there is any mistake again it has to go to the starting stage.
• SDLC is a long process generally taking months or years of times and during this time the client requirements may change or the project itself may not be viable due to change in market trend traditional models cannot adapt to these changes.
• In traditional model the client can only review the product only at end of project life cycle so there is no feedback or review from client or end users so the is a high risk the product not being successful after its released as it may look outdated.

Agile Methodology overcomes these problem in a quite flexible way such as:

• In Agile only small part of the actual product is made first which is generally called as a prototype and during these process the initial stages of SDLC can be repeated or step back if there is any mistake at any time.
• As only small part of the product is made first any new changes can be easily implemented and adopted into the project as an increment to the existing product.
• The prototype developed can be reviewed, tested and can even be deployed to the end users so that the developers can get feedback and reviews from end users and clients and develop the next increment to the product as per the feedback received so the risk of product being failed after release is vert minute.