Planning(SDLC)

The planning phase is the fundamental process of understanding why an information system should be built and determining how the project team will go about building it. It has two steps:

1. During project initiation, the system’s business value to the organization is identified: how will it lower costs or increase revenues? Most ideas for new systems come from outside the IS area (from the marketing department, accounting department, etc.) in the form of a system request. A system request presents a brief summary of a business need, and it explains how a system that supports the need will create business value. The IS department works together with the person or department that generated the request (called the project sponsor) to conduct a feasibility analysis. The feasibility analysis examines key aspects of the proposed project:
■ The idea’s technical feasibility (Can we build it?)
■ The economic feasibility (Will it provide business value?)
■ The organizational feasibility (If we build it, will it be used?)
The system request and feasibility analysis are presented to an information systems approval committee (sometimes called a steering committee), which decides whether the project should be undertaken.
 

2. Once the project is approved, it enters project management. During project management, the project manager creates a workplan, staffs the project, and puts techniques in place to help the project team control and direct the project through the entire SDLC. The deliverable for project management is a project plan, which describes how the project team will go about developing the system.

                                                                                                      Ref: System Analysis and Design

Software Development Life Cycle

In many ways, building an information system is similar to building a house. First, the house (or the information system) starts with a basic idea. Second, this idea is transformed into a simple drawing that is shown to the customer and refined (often through several drawings, each improving on the last) until the customer agrees that the picture depicts what he or she wants. Third, a set of blueprints is designed that presents much more detailed information about the house (e.g., the type of water faucets, where the telephone jacks will be placed). Finally, the house is built following the blueprints, often with some changes directed by the customer as the house is erected.
The SDLC has a similar set of four fundamental phases: planning, analysis, design, and implementation. Different projects may emphasize different parts of the SDLC or approach the SDLC phases in different ways, but all projects have elements of these four phases. Each phase is itself composed of a series of steps, which rely upon techniques that produce deliverables (specific documents and files that provide understanding about the project).

What is software Testing

Software testing is a process, or a series of processes, designed to make sure computer code does what it was designed to do and that it does not do anything unintended. Software should be predictable and consistent, offering no surprises to users.

Type of Requirement

Business Requirement:

   Business requirements represent a kind of "why" information. It represent the high level of objectives of the organization or customer who requests the system. Business requirement why the organization is implementing the system. Vision and Scope statement record the business requirement.

User Requirement

  Requirements constitute one type of "what" information. User requirements describe what the user will be able to do with the product, such as goals or tasks that users must be able to perform. Use cases, scenarios, user stories, and event response tables are some ways to represent user requirements.

Functional Requirement

      Functional requirement specify the software functionality that the developer must build into the product to enable the user to accomplish their business requirement . Functional requirements represent one kind of "what" information. The traditional "shall" statements that describe what the system "shall do" or what the system "shall let the user do.“

System Requirement

  Describe the top level requirement for a product that contain multiple subsystem that is a system. A system can be all software or it can be  both software and hardware.

Type of Requirement

There are various types of requirements:

Business Requirement

     Business requirements represent a kind of "why" information. It represent the high level of objectives of the organization or customer who requests the system. Business requirement why the organization is implementing the system. Vision and Scope statement record the business requirement.

User Requirement

      Requirements constitute one type of "what" information. User requirements describe what the user will be able to do with the product, such as goals or tasks that users must be able to perform. Use cases, scenarios, user stories, and event response tables are some ways to represent user requirements.

Functional Requirement

      Functional requirement specify the software functionality that the developer must build into the product to enable the user to accomplish their business requirement . Functional requirements represent one kind of "what" information. The traditional "shall" statements that describe what the system "shall do" or what the system "shall let the user do."

System Requirement

      Describe the top level requirement for a product that contain multiple subsystem that is a system. A system can be all software or it can be  both software and hardware.

 

Responsibilities of requirement analyst

Responsibilities:

1. Prepare Vision and Scope Statement.
2. Identify Project Stakeholders and User Classes.
3. Elicit Requirements.
4. Prepare Requirements Specifications(SRS).
5. Decompose high‐level business and user requirements into functional requirements.
6.  Define Quality attributes and nonfunctional requirements.
7. Lead requirements analysis and verification.
8. Requirement prioritization.
9. Peer reviews and inspections. 
10. Requirements traceability and track.
11. Change Management.
12. Reuse requirement.
13. Assist product management.

Requirement Analyst Job Description

The Requirement Engineer is the individual who has the primary responsibility to elicit, analyze, validate, specify, verify and manage the real needs.

Skill Needed:

1. Interview Skill.
2. Listening Skill.
3. Analytical Skill.
4. Facilitation Skill.
5. Observation Skill.
6. Writing Skill.
7. Modeling Skill.
8. Interpersonal Skill

Knowledge Needed:

1. Understanding Requirement Engineering.
2. Requirement engineering practices.
3. Product management concepts.
4. Application domain knowledge