Question

in your own words please , Discuss requirement structuring of Analysis phase of SDLC (activities and deliverables).

Answer 1

The software development life cycle (SDLC) is a process used for structuring the development of any software system, from initiation through to implementation. An increase in demand for software to meet customer needs effectively but with less cost and faster delivery, has put tremendous pressure on modern organizations. In order to stay competitive, companies need to correctly build their software, as well as transform their businesses by following efficient software engineering methodologies, practices, and concepts. If these the changes are not met, it can mean a drop in productivity and ultimately, the failure of the business. Customer interaction at all levels along with the right methodology for implementing the software, is crucial to the success of any organization.

SDLC is considered to be the foundation for all software development methodologies, with various activities associated with each level. Activities such as budgets, requirements gathering, and documentation writing, are included in the cycle, as well as the more technical elements.. The cycle ends when all requirements have been fulfilled. The software development life cycle comprises of seven distinct phases:

• Planning
• Analysis
• Design
• Development
• Testing
• Deployment
• Maintenance

• Analysis

In the analysis phase, end user business requirements are analyzed and project goals converted into the defined system functions that the organization intends to develop. The three primary activities involved in the analysis phase are as follows:

1.       Gathering business requirement
2.       Creating process diagrams
3.       Performing a detailed analysis

Business requirement gathering is the most crucial part at this level of SDLC. Business requirements are a brief set of business functionalities that the system needs to meet in order to be successful. Technical details such as the types of technology used in the implementation of the system need not be defined in this phase. A sample business requirement might look like “The system must track all the employees by their respective department, region, and the designation”. This requirement is showing no such detail as to how the system is going to implement this requirement, but rather what the system must do with respect to the business.

SDLC deliverables help State agencies successfully plan, execute, and control IT projects by providing a framework to ensure that all aspects of the project are properly and consistently defined, planned, and communicated. The SDLC templates provide a clear structure of required content along with boilerplate language agencies may utilize and customize. State agencies may use formats other than the templates, as long as the deliverables include all required content. The development and distribution of SDLC deliverables:

• Ensure common understanding among Planning Team members and stakeholders,

• Serve as a reminder of specified plans as projects become increasingly complex,

• Provide agency senior management and other State officials insight into project risks and ongoing performance,

• Encourage the execution of repeatable and consistent processes,

• Facilitate the implementation of project management and agency IT best practices,

• Result in a comprehensive record of project performance useful for many purposes (e.g. staff knowledge transfer, budgetary and other assessment activities, lessons learned). During the development of documentation, the Planning Team should:

• Write comprehensive, easy to understand documents with no redundant information. Single Release COTS Page 2 of 24 Phase 4: Requirements Analysis

• Develop an organized document repository for critical project information, so Planning Team members can easily access, store, and reference project documents and other deliverables from all life cycle phases.

• Implement routine deliverable reviews to correct inaccuracy, incompleteness, and ambiguities.

• Recognize that sample templates for deliverables are available; agencies might accept deliverables in different formats as long as all required information is present. The content of these deliverables might expand or shrink depending on the size, scope, and complexity of the project.

• Recycle or reference information from earlier documents where possible and beneficial.