Question

System Engineering Plan

Q1) It is recommended for the system engineering team to write a System Engineering Plan (SEP). Discuss the SEP and why it is needed throughout the System development life cycle

Requirements Analysis

Q2) In the requirements analysis stage, what are the major issues related to the users?

Software Design Methods

Q3) Discuss the Software Design methods used in Software Design.

Answer 1

1. Systematic engineering Plan:
Systems engineering can be thought as systematic engineering of a system through its
whole life cycle.
System Life Cycle requirements have a greater impact on the design, utilization, and disposal of the system.

->The Systematic engineering Plan is required because it captures the program's overall technical approach and integration
to program planning required to achieve the next MS.
->The Systematic engineering Plan captures and shares a roadmap of the technical execution of your program.
->Program personnel should use the Systematic engineering Plan as a reference to access information relative to the program.
->The The Systematic engineering Plan should be continuously updated as plans are modified.
And activities move from plans to historical facts known risks.
these are mitigated or significantly change to new risks.
For Identifying the New Risks new tools and technologies are adopted.
  
  
2.Issues of software Requirement Analysis:
software requirements analysis is process determining user expectations for a new or modified products.
which involves in gathering information about the customer's needs and defining Aspects.
It includes understanding the customer's business context and constraints
Even though This Phase of Software Developement process have some issues.
Issues:-
1.Customers don't know what they want:
Actually,The Customer Only knows what he want ?but He dont know what exactly he wants from the Product.
2.Customers have unreasonable timelines
3. Communication gaps exist between customers, engineers and project managers
4.The development team doesn't understand the politics of the customer's organization

3.Software Design:
Software design is a process to conceptualize the software requirements into software implementation
Which Follows the Divide And Conquer Strategy That is Divide the Problem into Some Small Valuable Modules.
and Each Sub Module is individually Developed.And Finally combined together for achieving a common Task.

A Software structured design always follows some rules for communication among multiple module.
1.Cohesion - grouping of all functionally related elements.
2.Coupling - communication between different modules.
One of the main components of software design is the software requirements analysis.
that is used to display the list of specifications used in software Engineering.
Software Design methods used in Software Design:
----------------------------------------------------
Mainly we are using three Types Of Methods in these.
1. Waterfall Model.
2.Spiral Model.
3.Rapid Application Developement
1. Waterfall Model:
-------------------
The waterfall model is a popular version of the systems development life cycle model for software engineering.
Often considered the classic approach to the systems development life cycle,
the waterfall model describes a development method that is rigid and linear.
Waterfall development has distinct goals for each phase of development
where each phase is completed for the next one is started and there is no turning back.

2.Spiral Methodology:
---------------------
The Spiral Lifecycle Model is a sophisticated lifecycle model that focuses on early identification and reduction of project risks.
A spiral project starts on a small scale, explores risks, makes a plan to handle the risks,
and then decides whether to take the next step of the project - to do the next iteration of the spiral.
It derives its rapiddevelopment benefit not from an increase in project speed,but from continuously reducing the projects risk level
which has an effect on the time required to deliver it.
Success at using the Spiral Lifecycle Model depends on conscientious, attentive, and knowledgeable management.
It can be used on most kinds of projects, and its risk-reduction focus is always beneficial.
3.Rapid Application Developement:
----------------------------------
Rapid Application Developement proposes that products can be developed faster and of higher quality by:
Using workshops or focus groups to gather requirements.
Prototyping and user testing of designs.
Re-using software components.
Keeping review meetings and other team communication informal.