Professional Documents
Culture Documents
I. INTRODUCTION
1. Purpose of Project
2. Scope of Project
V. SOFTWARE DESIGN
VI. CODING
THE PROTOTYPING MODEL: Often a Customer defines set of general objective for
software but does not identify Detailed input processing ,or output requirements .In other
cases the developer may be unsure of the efficiency of an algorithm, the adaptability of an
operating system, or the form that human/machine interaction should take. In these, and
many other situations, a prototyping paradigm may offer the best approach.
1) The prototyping paradigm begins with requirements gathering. Developer and
customer meet and define the overall objective for the software, identify whatever
requirements.
2) A “quick design” then occurs. The quick design focuses on a representation of those
aspects of the software that will be visible to the customer/user (e.g. input
approaches and output formats).The quick design leads to the construction of a
prototype
3) The prototype is evaluated by the customer and used to refine requirements for the
software to be developed. Iteration occurs as the prototype is tuned to satisfy the
need of the customer, while at the same time enabling the developer to better
understand what needs to be done. Ideally, the prototype server as a mechanism for
identifying software requirements.
a) When information that the product must be rebuilt so that high level of quality can be
maintained, the customer cries foul and demands that “a few fixes” be applied to make
the prototype a working product.
b) The developer often makes implementation compromises in order to get a prototype.
Personal information :
This module gives information about
2) Proposed System:
The purpose of this system have the capabilities allowing instructor the ability for
add, update, delete Student personal details for registration by implementing the methods
for reusability of the content. The student records system has been designed to be used and
understood by non-computer experts, means any student who has never used computer
before can feel compatible with this system. Movement around the system is facilitated
through a series of menus, which are accessed in a similar fashion at the level. Menu
selection as is becoming a standard in many software packages can carried out through
typing the highlighted number highlighted before the section.
Which inputs; in what form/format will inputs arrive; from what sources
Inputs
input will be derived.
Processing
Describes the outcome rather than the implementation; include any
validity checks on the data, hoe the handle unexpected or abnormal
situations.
The form, shape, destination and volume of the Output, unit measure of
Outputs the output; process by which the output is stored or destroyed; process
for handling the error messages produced as output.
Login Screen:
Fee Structure:
Inputs of this form are tution fee, hostel fee, Bus Fee, caution fee and
Inputs
mode of payment(DD, Cheque, Cash)
It sum up all the fee entries (Tution fee, Bus Fee, Caution fee, Hostel Fee)
Processing
and stores in total amount.
Outputs
Message box showing the status of payment whether paid or not.
Processing No Processing
Outputs No Outputs
Features Exit
2) Interface Requirements:
Interface of the Software Course Registration System with User, Software and
Hardware are specified as
1) Software Interface:
2) Hardware Interface:
RAM 512 MB
PROCESSOR PANTIUM 4 & ABOVE
HARD DISK 40 GB
3) Design Constraints:
1) Front End:
A front end refers to the client side end i.e., the end at which request is made. The
request is may originate in software are capable of sending it across to the server capable of
serving the request. There are many software packages that can serve as front end. Each
front end has its own features and tools for handling the data. We use the programming
language c++ as front end.
Use Case diagrams are formally included in two modeling languages defined by the OMG:
System:
Draw system's boundaries using a rectangle that contains use cases. Place actors outside the
system's boundaries.
Use Case:
Draw use cases using ovals. Label with ovals with verbs that represent the system's functions.
Actors:
V. SOFTWARE DESIGN:
Design Is the process of applying various techniques and principles for the purpose of
defining a device, a process or a system in sufficient detail to permit its realization .
A software decomposition into modules-description of what each module is
intended to do and of the relationship among the modules.
2) Architectural Design:
Architectural design consists of DFD. It depicts the relationship between major
“Structural Elements” of the software.
3) Interface Design:
Interface Design requires control specifications, state transition diagram and
DFD. It depicts the inter-communication path of software.
4) Component Level Design:
Component Level Design involves the control specification, state transition
diagram and process specifications.
INPUT/PROCESS/OUTPUT AT LEVEL N
4) Design Tools:
Tools available to support design are:
a) Data Dictionary
b) Abstract description of problem areas space in terms of:
Function and Performance
Data and Information Flow
Control Flow
Information Models
Objects/Attributes/Operation
Flow Diagram
Operational Timelines
Risk Analysis Charts
c) Information Compassion Tools
Decision Tables
Test Requirement Matrix
d) Support rationale Tools
Tradeoff matrices
Operational Timelines
e) Realization Tools
Flow Diagram
VI. CODING:
Code development is a practically implementation of the design in a specific
programming language.
Program Quality:
It is the collection of attributes of a program so that is makes itself able
enough to satisfy the need.
Program Quality Attributes of Course Registration System are:
PROGRAMME QUALITY ATTRIBUTES OF COURSE REGISTRATION SYSTEM
T
o
n
gE
f
M
sF
S
o
f
rt
t
u
m
w
a
rd
e
n
t
s
In the maintenance phase of this project errors are corrected which were not
discovered during its working life and tune the system to any variation in its working
environment.