PREPARING PROJECT
MCA MAJOR PROJECT
The Project:
Temporary
Definite
Beginning and
Ending
Unique
The Process
The Delivery
A project is a unique, transient endeavor, undertaken to achieve planned
objectives, which could be defined in terms of outputs, outcomes or benefits.
A success of Project is measurable on QoS Parameters.
The Project Characteristics:
The Project
Planning
The Project Development:
The Requirement Analysis:
The Feasibility Study:
The PROJECT SCHEDULING:
The PROJECT ANALYSIS:
The DATA FLOW DIAGRAM:
• A data flow diagram (DFD) is a graphical representation of the movement of
data between external entities, processes and data stores within a system.
• Simply put, DFD’s show how data moves through an information system.
9
The Process in DFD:
1.0
Grade Detail Grade Report
Produce
Grade
Report
– The work or actions performed on data so that they
are transformed, stored, or distributed.
– Process labels should be verb phrases!
10
The DATA FLOW in DFD:
2.1
Payment Detail
D1 Accounts
Post Invoice Detail Receivable
Payment
– A path for data to move from one part of the
system to another.
– Data in motion!
• Arrows depict the movement of data.
– NO VERBS
11
The DATA STORE:
D1 Students
– Used in a DFD to represent data that the system
stores
– Data at rest!
– Labels should be noun phrases
• (NO VERBS)
12
The EXTERNAL ENTITY
1.0
Order
CUSTOMER Invoice
Verify
Order
– The origin or destination of data!
• This represents things outside of the system.
– Source – Entity that supplies data to the system.
– Sink – Entity that receives data from the system.
– The labels should be noun phrases!
13
The General DFD Rules:
YES NO
A process to another process
A process to an external entity
A process to a data store
An external entity to another external entity
An external entity to a data store
A data store to another data store
14
Online Vehicle Repair & Maintenance:
Chronic Kidney Disease DFD:
DFD Levels:
DFD Levels:
DFD Levels:
The Software Modules:
The System Architecture:
The UML DIAGRAM:
• Standard language for specifying, visualizing, constructing,
and documenting the artifacts of software systems, business
modeling and other non-software systems.
• The UML represents a collection of best engineering practices
that have proven successful in the modeling of large and
complex systems.
• The UML is a very important part of developing object
oriented software and the software development process.
• The UML uses mostly graphical notations to express the
design of software projects.
• Using the UML helps project teams communicate, explore
potential designs, and validate the architectural design of the
software.
The UML DIAGRAM:
Behavioral
: behavioral features of a system / business
Structural process
: element of spec. irrespective of time
• Activity
• State machine
• Class
• Use case
• Component
• Interaction
• Deployment
• Object
• Composite structure Interaction
• Package : emphasize object interaction
• Communication(collaberati
on)
• Sequence
• Interaction overview
• Timing
The CLASS DIAGRAM:
The CLASS DIAGRAM:
The DEPLOYMENT DIAGRAM:
The DEPLOYMENT DIAGRAM:
The PROCCESS DIAGRAM:
The STATE TRANSITION DIAGRAM:
• UML 2 State machine diagrams can show
the different states of an entity also how
an entity responds to various events by
changing from one state to another. The
history of an entity can best be modeled
by a finite state diagram.
THE STATE MACHINE
The STATE DIAGRAM:
The USE CASE DIAGRAM:
UML 2 Use cases diagrams describes the behavior
of the target system from an external point of
view. Use cases describe "the meat" of the actual
requirements.
• Use cases. A use case describes a sequence of
actions that provide something of measurable
value to an actor and is drawn as a horizontal
ellipse.
• Actors. An actor is a person, organization, or
external system that plays a role in one or more
interactions with your system. Actors are drawn
as stick figures.
• Associations. Associations between actors and
use cases are indicated by solid lines. An
association exists whenever an actor is involved
with an interaction described by a use case.
The USE CASE DIAGRAM:
The USE CASE DIAGRAM:
The USE CASE DIAGRAM:
The SEQUENCE DIAGRAM:
• UML 2 Sequence diagrams models the
collaboration of objects based on a time
sequence. It shows how the objects
interact with others in a particular
scenario of a use case.
The SEQUENCE DIAGRAM:
The DATA DICTIONARY:
ER DIAGRAM SYMBOLS:
BUS TICKET BOOKING:
HOTEL BOOKING:
ER FRAMEWORK DIABETESE PREDICTION :
The Software Testing:
The Test Case Description:
The Maintenance Plan:
