URS and SRS

We have two requirements specifications. One is User Requirements Specification (URS) aimed at
capturing the needs of the end users. The other is Software Requirements Specification (SRS). All the user
information collection is bundled into URS, it is a view of the End Users and is somehow non-technical in
the sense that we do not keep in mind the characteristics of a software. Whereas the Software
Requirements Specification (SRS) is prepared to keep in mind the development of an application. Software
Requirements Specification (SRS) is prepared to aim that this is to be transformed into the Design and
Construction.

Analysis Models
Software requirements analysis enables us to make the Analysis Models diagrams which are transformed
into the Software Design.
Data/Class Design
First step in design activity is to build a software class design. It contains a hierarchical structure of the
classes to be build. It also give the details of the classes. Major input to this design are Class diagrams and
CRC cards.

Architectural Design
Software architecture provides the structure and organization of software components, their properties,
and the connections between them. It includes the details of the coding elements, like Classes, their data,
methods, modules, and functions. Different UML diagrams like the class diagrams, state charts,
components and collaborative diagrams are used to represent all the architectural aspects. First of all
system is shown as at context level (i.e. The Context Level DFD).

Next, for the detailed architectural design a data flow diagram (DFD) is mapped into a complete program
structure (i.e. the software modules). The DFD is mapped into a program structure that allocates control
to input, processing, and output by providing the level-2, level-3 or even level-4 DFD.
Interface Design
The user interface is the most important element of a computer-based system or product. If the interface
is poorly designed, the user’s ability to tap the computational power and informational content of an
application may be severely hindered. This provides a basis for the creation of a screen layouts that depicts
graphical design and placement of icons, screen texts, titling for windows, and specification of major and
minor menu items. Design issues such as response time, command and action structure, error handling,
and help facilities are also considered here as the interface design model is refined.

Component Level Design

Component level design is the design of components and modules after the architectural design phase.
Component-level design defines the detailed level of data structures, algorithms, interface characteristics,
return calls, and the communication mechanisms allocated to each component for the system
development. Component level design now gives the details of Pseudocodes, which includes: variables
types, conditionals, loops, and similarly, the details of other programming elements, like databases,
arrays, file handlings, etc.