Requirement

You might also like

Download as odt, pdf, or txt
Download as odt, pdf, or txt
You are on page 1of 4

Requirement (Software Development

LifeCycle)
• Table of Contents (Full Assignment)

• Table of Contents (For Image)

• Background(Full Assignment with scenario)

• Objective

• Part 1

Prepare Report

Cover Page (Title , Submitted by , Submitted of , Date )

Table of contents (part 1)


Executive summery
Objective
Scope

• P1:-introduction (SDLC )

Start your task based on scenario.


iterative model-discuss
types-discuss:
1.agile model
overview
model
advantages and disadvantages
2. spiral model-discuss/overview
ad/disadvantage
functional
sequential model discuss
types:
1. waterfall model-overview
ad/dis
2. v-model
ad/dis

• M1:
• for all set examples too
for merit just include
select the best model from upper one
and discuss how it will be better for scenario
with example/evidence.
based on flexibility/collaborative/transparent/result oriented
• P2:
• write down all risks over the model/selected model
abd also find out solution for that based on scenario only
• D1:
Using Clear structure:
Easy to follow
No overlapping
Determines the end goal early
Easy to arrange task

Part 2:-
• explain the importance of a feasibility study.

• produce a documentation:

• Cover page

1. Documentation title.
2. Published by .
3. Published date.

Table of Contents (Part2)

Introduction (part 2)

Overview (question related )

P3: what do you mean feasibility study, types , propose(type and on the basis of
scenario)

Type :-technical feasibility:-

,Economic,legal,operational ,scheduling

P4:-tool and technology ,time frame , feasibility of project,

M2:-components:-purpose of scope,Current Analysis,Requirement,Evaluation,Review.

D2:- impact of different feasibility:-Technical impact,Economic Impact, Operational


Impact,Legal Impact,Scheduling impact
Part3:-

cover page

P5:
Background of example software
problem statements
software automated, employee auto, salary slip,attendance, performance...
data collection process
investigation scenario for example (visiting , online interview )
summary-merit will include and demerit will explore.

P6:

Here are some commonly used software analysis tools/techniques to carry out a
software investigation:
Data Flow Diagram (DFD)
Entity-Relationship Diagram (ER Diagram)
Flow chart
Data Dictionary
M3:

Requirements traceability (overview )


Bi-directional traceability:Like Forward traceability and Backward traceability

M4:
what do mean by improvement
overview
list approach
select any two approach and discuss with function and benefits

D4:
activities for completing the approach of improvement
like information gathering

Part4:-
overview of s/w requirement and why we required s/w requirement during
development
software overview
requirement list
table- client requirement vs actual task
M5:
discus range of tools and technique
flowchart/dfd/pseudo code
overview
diagram as per scenario
M6:
discuss fsm and efsm
Differentiate between a finite
state machine (FSM) and an
extended-FSM,
providing an
application for both

Best Of Luck

You might also like