Part: 1

 Introduction
 Software development lifecycle models: Definition and list about existing models.
 Iterative models
- Definition ,
- Steps in iterative methods
- Diagram if possible
Two iterative models
For each iterative methods you must include:
- Definition
- Steps or process in this method
- Diagram of the models
- Pros and Cons of this model
 Sequential model
- Definition
- Steps in Sequential method
- Diagram if possible
Two sequential models
For each sequential methods you must include:
- Definition
- Steps or process in this method
- Diagram of the models
- Pros and Cons of this model
 Spiral lifecycle
- Definition
- Identify and resolve risk
- Define and clarify how requirement are identified and how risk are resolved in
spiral models
- Risk management in Spiral model
- Explain What type of risk are handle in this model
 Selection of models for development environment & How you choose
 Merits of applying waterfall models to a large software development project
 Conclusion
Part 2

Topic Sub Topics Details

Introduction
Feasibility 1. Define Explain each purpose in
Reports 2. Purpose of Feasibility Study. brief
Technical 1. Defination
Solutions 2. Comparision of Technical Solution based
on
1. Budget
2. Performance
3. Efficiency
4. Automation
5. Legacy
6. Elimination of Human Errors

Components of Explain all in brief

Feasibility
Reports
Impact of 1. Economic Criteria Include Following Topic for
Feasibility 2. Technical Criteria each Criteria
criteria on 3. Time Criteria 1. Definition
Software 4. Legal Criteria 2. Finding the existing
Investigation 5. Operational Criteria criteria for each
6. Social Criteria 3. How you implement in
7. management criteria your scenario
4. Analyze how you tried
to meet different
criteria mentioning the
Problems encounter
and Solution you
applied

Conclusion
Part 3

Introduction

3.1 Identification of stakeholders

Define Stakeholders and Discus about the stake holders that exist in your Research work of system

Identify the requirements of the client

Identify the requirement after gathering information from the stake holders

Specification of scopes

Define what is scope of projects? Mention the scope of your given scenerio

Inputs, outputs, processes and the process descriptors

Define the above terms. Determine what are the inputs, outputs and process involves in your system.
The format can be as follows..

Consideration of alternative solutions

What is the current solution selected and what can be the alternative solution if it fails in system?

Security considerations

What is security concern in system? How you have tried to applied security measures in your system.
 Use of quality assurance

What is Quality assurance? How you did Quality assurance in your system.

Identification of different constraints

What is constraint? What were the constraints in the following topics?

1. Cost
2. Legacy
3. Organizational policy
4. Hardware requirement

Explain what the limitation were and how they were overcome

3.2 Background information

Introduce the company with its nature of work and how it is going on at current context.What work are
done in this organisation.What were the difficultiies and what is the purposed system supposed to do.

Problem statements

What are the problem with the current system of working? What caused the less efficiency in delivery of
service in the company.

Data collection process

What are the requirement gathering process you used? Explain all gathering process. Attach the
evidence of gather data at least for 2 methods.

Data flow diagram

Draw flochart of DFD level 0(context diagram),level 1 and level 2

Entity Relationship Diagram

Mention all symbol .Draw Er diagram of the system.

Summary

Write summary of background information

3.2 Requirement tracing

Write about the requirement tracing and follow the requirement tracing process as sample given below

3.3 Approaches to improve software quality

Research and write how you can approach to improve the software quality such as
1. Employ test-oriented software development management
2. Report bugs effectively
3.

3.4 Function design paradigm

write about it

Use of function design paradigm in the software development lifecycle to improve software
quality

Write how function design paradigm is used in your scenario.

1. Answer following based on feature

2. Which model you have used for project and why depending upon the feature
3. What is the significance of making DFD, ERD in the project?

Conclusion
Requirement tracing sample
In the software of insurance company, we have done difference requirement tracing too. Among them,
there requirement tracing of login to the software is given below:
While requirement testing, there should be need on business requirement document and technical
requirement document by which the testers starts writing test cases. A business requirement document
(BRD) details the business solution for a project including the documentation of customer needs and
expectations whereas a technical specification document defines the requirements for a project,
product or systems. Now, let’s suppose, the following table is the business requirement document for
insurance company software:

Business Module Applicable

Description
Requirement Name Roles
B1 Login Manager, Customer: A customer can login using the
(Business Customer login page
requirement for Manager: A manager can login using the
insurance company login page of customer. Post login
software) homepage will show the different links
based on role

In the above table, it is showing that the customer should be able to login to insurance company
software with the correct password and user_id whereas manager should be able to login to the
insurance company software through customer login page. The technical requirement document of the
insurance company software is given below:

Login
T92 => User_id must not be blank
T93 => Password must not be blank
T94 => If user_id and password are valid => Login

Now the requirement tracing of the insurance company software is given below:
Step 1: “Verify Login, when the correct user_id and Password is entered, it should log in successfully”
S.N. Test Case Test Steps Test Data Expected Result
1. Verify Login 1. Go to login page User_id = Susan7872 Login Successful
2. Enter user_id Password =
3. Enter password Susan7878@
4. Click login
If the email and password is
correct, It should login
successfully.
Step 2: Identify the technical requirement that this test case is verifying. For the test case, the technical
requirement is T94 is being verified.

T94 => If user_id and password are valid => Login

T94 is technical requirement that
That verifies successful login

Step 3: Note technical requirement (T94) in the test case:

Expected
S.N. TR# Test Case Test Steps Test Data
Output
1. T94 Verify Login 1. Go to login page user_id = Susan7872 Login Successful
2. Enter user_id Password =
3. Enter password Susan7878@
Note the technical 4. Click login
Requirement In
the test case
Step 4: Identify the business requirement for which this technical requirement (T95) is defined
Business Module Applicable
Description
Requirement Name Roles
B1 Login Manager, Customer: A customer can login using the
(Business Customer login page
requirement for Manager: A manager can login using the
insurance company Identify the business
login page of customer. Post login
software) homepage will show the different links
Requirement for
based on role
which T04 is defined
Step 5: Note this business requirement in test case
Expected
S.N. BR# TR# Test Case Test Steps Test Data
Output
1. B1 T94 Verify Login 1. Go to login user_id = Susan7872 Login Successful
page Password =
2. Enter user_id Susan7878@
3. Enter
password
4. Click login

Step 6: Do above for all test cases, later extract the first 3 columns from the test suite.
Business Requirement # Technical Requirement # Test Case ID
B1 T94 1
B2 T95 3
B3 T96 3
B4 T97 4
Thus, these are the complete example of the requirement tracing which was done for the login page of
the insurance company software. It is the most important to do the requirement tracing. It helps to
highlights any requirements missing or document inconsistencies. It also helps in analyzing or estimating
the impact on the GA team’s work with respect to revisiting or re-working on the test cases and shows
the overall defects or execution status with a focus in business requirements.
Part: 4

Introduction

4.1 Documentation of user and system requirements

Describe its importance

Tabulation of the expected client requirements and the actual output of the product

S.N. Expected client requirements Actual output

1. Easily access to the international market There is automatically conform and easy
access to the international market with the
collaboration and associated with the
international market.
2
3

4.2 Software specification

1. Define and write its benefits

2. Explain different specification method such as flow chart and pseudo code.
3. draw flow chart and write pseudocode for 3,4 module

4.3 Finite state machine (FSM)

Deterministic finite automation

Nondeterministic finite automation

Applications of finite state machine

Extended finite state machine

Application of extended finite state machine

4.4 Data driven software

Definition and Application

Improving the reliability and effectiveness of the software using data driven software

Conclusion

Bibliography