In software development
project design document is one of the basic and most import thing because it
tell us that what our end product is going to look like in this phase of
project many thing about are project is revealed and this document tell the
user that how our program is going to work what are the basic thing from which
our product is made of or in other word it is the blue print of our project
that what can our program can or cannot do ,what are its limits and what action
it can perform and what are the benefits of using this program. Designing
software is one of the main goals which one should have close eye on because if
your design is good the end product will also going to be a great one.
Designing software is progress by large number of iteration in this phase the
software developer analysis the system and calculates all the aspects of the
system.
In this process there are
many numbers of different models that shows us the different aspects of our
system .we judge our system by applying different kind of techniques to check
the level of concepts in our system. These models that are used throughout
requirement engineering domain models are the go together.
At this level the design of
the software architecture is shown by the separating the system into different
subsystem or models and their interferences with each other.
Data modeling is also an
essential activity performed during the design phase. This includes the
identification of data entities and their attributes, relationships among these
entities, and the appropriate data structures for running this data.
In design phase we determine
the functional and non functional requirement of our project. We also determine
the business purposes with respect to software development .Design phase
explain the activities and tasks which are necessary during the completion of
our project.
Following are
the things which are included in this phase
·
Entity Relationship Diagram (ERD)
·
Sequence Diagrams
·
Architecture Design Diagram
·
Class Diagram
·
Database Design
·
Interface Design
·
Test Cases
Entity Relationship Diagram (ERD)
Entity-relationship
(ER) diagram is a graphical
representation of entities and their relationships to each other. An entity is
a piece of data-an object or concept about which data is stored. A
relationship is how the data is shared between entities.
There are
three types of relationships between entities:
·
One to One
·
One to many
·
Many to many
One to one
In this relation a single entity
has one relation

One-to-Many
In this relation a single entity has many relation

Many-to-Many
In this relation many entity has many relation with each other.

Sequence Diagrams
A sequence diagram is a kind
of interaction diagram that shows how processes operate with one
another and in what order. It is a construct of a Message Sequence Chart.
A sequence diagram shows object interactions arranged in time sequence.
Sequence diagrams are typically associated with use case realizations in the
Logical View of the system under development. Sequence diagrams are sometimes
called event diagrams or event scenarios.
Architecture Design Diagram
An architectural model is a rich and
rigorous diagram which is created using available standards in which the
primary concern is to illustrate a specific set of tradeoffs inherent in the
structure and design of a system or ecosystem. An architectural model is an
expression of a viewpoint in software architecture.
Class Diagram
A class diagram in the Unified
Modeling Language (UML) is a type of static structure diagram that
describes the structure of a system by showing the system's classes and their
attributes, operations and the relationships among objects.
Database Design
Database
design is the process of producing a
detailed data model of a database. This logical data
model contains all the needed logical and physical design choices and
physical storage parameters needed to generate a design in a Data
Definition Language. This can then be used to create a database.
Interface Design
Interface
design deals with the process of
developing a method for two or more modules in a system to connect and
communicate. These modules can apply to hardware, software or the interface
between a user and a machine.
Test Cases
A test case is a set of conditions or
variables under which a tester will determine whether
an application software system or one of its features is working
as it was originally established for it to do.
No comments:
Post a Comment