Nt1310 Unit 1 Module Analysis

Combining views
By adopting layers as the basic component of work assignment and implementation, we will combine the allocation views (implementation and work assignment) with module views (decomposition) for each stakeholder. Before the work assignment is assigned a value it is important to know which module is allocated to which layer. This way module decomposition and layers go along with each other and by making this decision it reduces three views from the system architecture.
Rationale
Reason behind choosing the component and connector view is to display the concurrent process execution between the system components. As we explained,system is the embedded system. So it is obvious that it is divided in two parts where one is the user and on the

Iterative and incremental approach is a better way of developing requirements and modules as well.
4. Requirements provide a complete operating picture of the solution, which helps in taking correct decisions during initial stages of software development life cycle (SDLC).

Iterative and Incremental Approach
This approach allows us to make changes before it is too late.

Identifying user classes is always the first and the foremost thing to be determined by the requirement analyst before starting the work on the project.A product champion is highly important in Software development life cycle. It often becomes very difficult to gather requirements from a different people with diverse thought process who belong to a single user class. It is important to have a single point of contact from the users’ side for the developers and analysts to discuss requirements in detail. Product champion conveys the voice of the user to the development team clearly.
Activity and Schedule
An indicative activity schedule is provided below:

S. No Activity (work) Months from the start of assignment M1 M2 M3 M4 M5 M6 M7 M8
1
- Preparation of SRS
- Preparation of Design Document
- Approval
System