Project Report Course Registration System
Project Report Course Registration System
Feasibility study
• Technical Feasibility
• Economic Feasibility
• Operational Feasibility
• Social Feasibility
System Analysis
• Problem definition
• Problem analysis
• Analysis issues
• Requirements process
• Requirements determination
• Requirements Anticipation
• Requirements Investigation
• Requirements Specification
Testing
References
Future Enhancement
Appendix
References
Introduction
With this changing world we also have to change ourselves according to the
current requirements of the market, there was no proper medium available for the people
to get information about the world so that they could update theirseleves besides news
paper, but today various medium area there such as television, radio and now a days IT.
IT has changed the people's idea about information. People can get information about any
thing within few seconds. These medium are the software which are developed to store
information about any particular area. Here, the software CR will help the student to get
the information about a particular course and then they can easily register them self in a
particular course. The management of the institution can easily see the records of the
students and course and fees.
CANDIDATE’S DECLARATION
Mr.
Date:
CERTIFICATE
Mr.
(PROJECT GUIDE)
BIT, MEERUT
Requirement Tool & environment
Front end
Visual Basic 6.0
Back End
Ms Access
As a front end, visual basic 6.0 support our project environment because:
Feasibility Study
TECHANICAL FEASIBILITY:-
The proposed project is user friendly as well as easy to operate. It is a menu driven
software which a layman can also operate, so it is very easy for the user to know and run
the software in technical feasibility configuration of the system is given more importance
than the actual make of hardware. The configuration should give the complete picture
about the system requirements like—many work stations are required, how these units
are interconnected so that they could operate and communicate smoothly. What speed of
input and output should be achieved at particular quality of printing?
ECONOMIC FEASIBILITY:-
Financial benefits arising are more since any already installed hardware can be used and
software investments is almost negligible, as the software can be run on any operating
system which is already there in the machine. User can be trained to use the system in
very less time and cost, thereby increasing the profit. The proposed project is
economically feasible. Economic analysis is the most frequently used technique for
evaluating the effectiveness of the proposed project more commonly know as cost benefit
analysis. The procedure is to determine the benefits and savings that are expected from a
proposed project and compare them with the cost.
OPERATIONAL FEASIBILITY:-
Operational feasibility is mainly related to human organizational and political aspects.
Our project is operationally feasible because all type of user can use or work in our
project. The main points which are considered in our project to make it operationally
feasible are
1- There is sufficient support for the project from the management. The current
project is well like and used to the extent that users will not be able to see reasons
for a change.
2- The current project have the methods acceptable to the users, there are some
facilities in the project that the user may welcome a change that will bring about a
more operational and useful system according to there needs.
3- The proposed system does not cause any harm and it will produce better results in
any respect or area. The proposed project provides high performance in all areas
and will not affect any customer in an undesirable way.
SOCIAL FEASIBILITY:-
The current project is socially feasible because it is acceptable by all the user, the
determination examined that the probability of the project is being accepted by the
group directly affected by the proposed project change.
SYSTEM ANALYSIS
This section overviews systems analysis and design and describe the work of system
analysts & the different types of users that participate in the development process.
PROBLEM DEFINATION:-
This is initial and essential step in planning software project before starting work on
the project ATM SYSTEM, some questions arises in my mind that what is the actual
problem and how could I solve it? What are he characteristics of the entity that I can
use to solve the problem? How will the entity and the solution realized? What
approach will be used to solve the unclear errors that were made while designing &
doing construction of the entity? How wills the entity, we supposed over the long,
when correction, adaptation and enhancements are requested by the user? After
knowing the actual problem I define some point for the problem definition, I develop
a definite statement of the problem to be solve including description of the present
situation, problem constraints and a statement of the goals to be achieve, I though a
computerized solution strategy for the problem, identification of the function, to be
provided by hardware, software and programmer establishing high level acceptance
criteria for the system.
PROBLEM ANALYSIS: -
The basic of problem analysis is to obtain a clear understanding of the needs of users,
what exactly is desired from the software analysis leads to the actual specification,
analysis involves interviewing the clients & end users. These people & the existing
documents about the current mode of operation are the basics source of information
for the analysts. Typically analysts research a problem by asking question from users
and by reading existing documents. The process of obtaining answers to question that
might arise in my mind continues until I felt that all the information has been tainted,
as the clients and the users do not understand or know all their needs, because the
potential of the new system is often not fully appreciated although I have ensured that
the real needs of the clients. And the users are covered by this project because I have
played an active role of helping the clients & users to identify their needs by acting as
a consultant.
ANALYSIS ISSUES:-
The software requirement is dealing with the requirement of the proposed system,
that is, the capabilities that the system which is yet to be developed, should have. It is
because we are dealing with specifying system that does not exit in any form the
manual form of existence does not generally have the same capability as the eventual
automated system that the problem of requirement becomes complicated. This
happens more in complex application where all the needs many not be know to any
set of people during the requirement phase. The problem gets worse because
frequently the SRS and the process of requirement analysis and specification give
additional ideas to client about what is needed from the system changing requirement
is a continuous irritant for software developer and frequently leads to bitterness
between the user and developer through may changes come due to the changing needs
of the user many of the change request have their origin in incorrect interpretation or
specification of the requirement these errors come in the SRS largely due to the
requirement analysts not performing the task rigorously.
The origin of this project is in the need of a client, who either wants to automate an
existing manual system or desires a new project. The proposed system itself is created
by the developer. Finally, the completed system will be used by the end user. Thus,
three major parties interested in a new project are the client, the user and the
developer. Somehow the requirements for the system that will satisfy the needs of
the clients and the concern of the user have to be communicated to the developer. The
problem is that the client usually does not understand process and the parties involved
In order to satisfy the client which is the basic quality objective of project
development, the user has to be made aware of these potential and aided in
visualizing and conceptualizing the needs and requirement of his organization.
The process of developing an SRS usually helps in this, as it forces the users to think,
visualize, interact, and discuss with others to identify the requirement therefore as
SRS establish the basis for agreement between the clients and the supplier on what
the software service will do. In SRS provides a reference for validation of the final
service.
That is the SRS helps the client determine if the project meets the requirement
without a proper SRS, there is no way a client can determine if the project being
delivered is what the ordered is. And there is no way the developer can convince the
client that all the requirements have been fulfilled.
REQUIREMENT PROCESS:-
The requirement process is the sequence of activities that need to be performed in the
requirements phase and that ultimate in providing a high- quality document
containing the project requirement, where as the process ends in producing an SRS,
its starting point depends on whether the project to be developed is a stand- alone
project problem only or is one in which project is a component of the system that
requires a combination of hardware and software.
The requirement process starts when the problem has been identified or a new idea
for software arises. Where a system comprising hardware and software is expected to
form the solution of the problem at hand the starting point of the project is the
requirement specification that are need while maintaining the record of services.
The organization of this project is originally in the mind of the user and customers. I
have ensured that as far as possible all the requirements of the project are detected
and analyzed, clearly specified in the document describing the SRS, and that the SRS
if of high quality. In the requirement phase I have faced three basic activities problem
or requirements validation. The first aspect, perhaps the hardest and most nebulous
that I have deal with understanding the problem, the goal, the constraints etc. During
analysis the problem domain and the environment are modeled in efforts to
understand the system behavior, constraints on the system, its inputs and outputs etc.
The basic purpose of this activity is to obtain a through understanding of what the
project needs to provide.
The second activity that I have define is the requirement specification which I have
focused clearly by specifying the requirement in a document, such as representation,
specification language, and tools, are addressed during this activity I have produced
large amount of information and
Requirements Determination:
Requirements determination involves studying the current business system to find out
how it works and where improvements should be made system studies results in an
evolution of how current methods are working and whether adjustments are necessary
or possible. These studies consider both manual and computer methods. As we shall
see; these are not merely computer studies;
A requirement is a feature that must be included in a new system. It may include a
way of capturing or processing data, producing information controlling a business
activity, or supporting management.
The determination of requirements thus entails studying the existing system and
collecting details about it to find out what these requirements are it is helpful to my
requirements determination through the three major activities of requirements
anticipation requirements investigation and requirements specification knowledge
with possible redundancies, properly organizing and describing the requirements as
an important goal of this project.
The final activity is focused on validity that what has specified in the SRS are indeed
all the requirements of the project and making sure that the SRS is of good quality.
The requirement process terminates with the services of the validated SRS. If the
objective is to define the overall broad needs of the systems the requirements can be
very abstractly stated. Generally the purpose of such requirement is to perform some
feasibility analysis or use the requirements for competitive bidding.
At the lower level are the requirements where all the behavior are clearly specified
such requirements are clearly very details and are suitable for software development
it can be seen that the requirements at the lower level can be viewed as specifying the
how, when viewed from the higher level of abstraction.
Requirements Anticipation:
It can be a missed blessing on the one hand experience from previous studies can lead
to investigation of areas that would otherwise go unnoticed by an inexperienced
analyst.
Having the background to know what to ask or which aspect to investigate can be a
substantial benefit to the organization. On the other hand, if a bias is introduced or
shortcut are taken in conducting the investigation, requirements anticipation is a
problem. We will point guidelines for structuring an investigation around basic
questions to avoid the undesirable consequence of requirements anticipation.
Requirements anticipation
It can be mixed blessing on the one hand, experience from previous studies can lead
to investigation of areas that would otherwise go unnoticed by an inexperienced
analyst.
Having the background to know what to ask or which aspect to investigation can be a
substantial benefit to the organization. On the other hand, if a bias is introduced or
shortcuts are taken in conducting the investigation, requirements anticipation is a
problem.
We will point guidelines for structuring an investigation around basic question to
avoid the undesirable consequence of requirements anticipation.
Requirements Investigation:-
This activity is at the heart the system analysis. Using a variety of tools and skills,
analyst studies the current. System and documents its features for further analysis.
Requirements investigation relies on the fact finding techniques and includes methods
for documenting and describing system features; the structured analysis strategy for
requirements investigation.
Requirements Specification:-
The data produced during the fact finding investigation are analyzed to determine it,
the description of features for a new system. This activity has free for interrelated
parts:
Analysis of factual data- the data collection during the fact finding study
include in data flow and design analysis documentation are examined to
determine how well the system is performing and whether it will meet the
organization demands.
Identification of the essential requirements features that must be included in a
new system, ranging from operational details to performance criteria, are
specified.
Selection of requirements fulfillment strategies the methods that will be used
to achieve the stated requirements are selected these from basis the system
design which follows requirements specification.
SYSTEM DESIGN
The design activity begins when the requirement document for the software to be
developed is available. This may be the SRS for the complete system, as is the case if
waterfall model is being followed or the requirements for the next” iteration” if the
iterative enhancement is being followed or the requirements for the prototype if the
prototyping is being followed.
While the requirement specification activity is entirely in the problem domain, design is
the first step in moving from the problem domain toward the solution domain design is
essentially the bridge between requirement specification and the final solution for
satisfying the requirements.
The term design is used in two ways. Used as a verb. It represents the process of design.
Used as a noun, it represents the result of the design process, which is the design for the
system. The goal of the design process is to produced a model or representation of a
system, which can be used later to build that system. The produced model is called the
design of the system. The design of a system is essentially a blue print or a plan for a
solution for the system. Here was consider a system to be a set of components with
clearly defined behavior that interacts with each other in a fixed defined manner to
produce some behavior or services for its environment manner to produce some behavior
or services for its environment. A component of a system can be considered system, with
its own component. In a software system, a component is a software module. The design
process for software system often has two levels .At the first level the focus is on
deciding which modules are needed for the system, the specification of these modules,
and how the modules should be interconnected. This is what is called the design or top
design. In the second level, the internal design of the modules, or how the specification of
the module can be satisfied, is decided. This design level is often called detailed design or
logic design. Detailed design essentially expands the system design to contain a more
detailed description of the processing logic and data structure so that the design is
sufficiently complete for coding. Because the detailed design is an extension of the
system design, the system design controls the major structural character tics of the
system.
The system design has a major impact on the testability and modifiability of a system,
and it impacts its efficiency. Much of design effort for designing software is spent
creating the system design.
A design methodology is a systematic approach to creating a design by applying of a set
of techniques and guidelines. Most design mythologies essentially offer a set of
guidelines that can be used by the developer to design a system. These techniques are not
formalized and do not reduced the design activity to a sequence of steps that can be
followed by the designer.
The input to the design phase is the specification for the system to be designed. Hence a
reasonable entry criteria can be that the specification are stable and have been approved ,
hopping that the approval mechanism will ensure that the specification are complete,
consistent, unambiguous, etc. the output of the top level design phase is the architectural
design or the system design for software system to be built. This can be produced with or
with out using a design methodology. Reasonable exit criteria for the phase could be that
the design has been verified against the input specification and has been evaluated
approved for quality.
A design can be object – oriented or function – oriented. In function – oriented design,
the design consists of module definition, with each module supporting a functional
abstraction. In object – oriented design, the modules in the design represent data
abstraction (these abstractions are discussed in more detail later).
In a function – oriented design approach, a system is viewed as transformation function,
transforming the inputs to the desired outputs.
The purpose of the design phase is to specified the component for this transformation
function, so that each component is also a transformation function. hence, the basic
output of the system design phase, when a function oriented design approach is being
followed, is the definition of all the major data structures in the system , all the ,major
modules of the system , and how the modules interact with each other.
OBJECTIVES IN DESIGNING:-
Requirement is translated into design specification. What does the system analysts intend
to achieve when design an information system? This section describes the objective of
system design and explores the nature of the design, as wall as the explicitly result
expected.
System design involves first logical design and then physical construction of the system.
When analysts formulate a logical design, they write the detailed section for the system;
they describe its features the output, input files and database, and procedures all in a
manner that meets project requirement.
The statement of this feature is turned the design specification of the system. The
logical design of an information system is like the engineering blueprint of an
automobile, it shows the major features (such as the engine, transmission and passenger
area) and how they are related to one another (where components interconnect or how far
apart the doors will be).
The reports and the outputs of the analysts are like the engineers design component. Data
and procedures link each together to produce a working system. Physical construction the
activity following logical design, produce program software files and a working system.
Design specification instructs programmers about what the system should do. The
programmers in turn write the programs that accept input from users, process data,
produce the report, and store data in the files. The physical design for the sample service
of this project introduce above consist of programs steps, written in a programming
language.
These steps revise record of quantities on hand by using transaction data, print the reports
and store the data. The analysts specify the algorithm for changing the stock quantities.
During physical construction, programmers write the program instruction to compute the
change and produce the result.
The components of an information system described during requirement analysis are the
focal point in system design. Analysis must design the following elements.
• Data flow – the movement of data into, around, and out of the system.
• Data stores – temporary or permanent collection of data.
• Processes –activities to accept, manipulate, and deliver data and
information, may be manual or computer based.
• Procedures – methods and routines for using the information system to
achieve the intend results.
• Controls – standards and guidelines for determining whether activities are
occurring in the anticipated or accepted manner, that is, “under control” also
specifies actions to take when problems or unexpected circumstances are
detected. May include the reporting of exception or procedures for
correcting problems.
• Roles – the responsibilities of all persons include with the new system,
including end – users, computers operators and support personnel. Span the
full spectrum of system components, including input of data to distribution
of output or results roles are often stated in the procedures.
Design-Oriented design:
Object oriented approaches are getting a lot of attention these days. Many
claims have made in support of object –oriented approaches. One main claimed
advantages of using object orient aches is that an object oriented model closely
represents the problem domain , which makes it easier to produces and
understand design
Testing
In this test process to class inputs were taken they are; software configuration that
includes software requirements specification design specification and source code.
Test configuration- that includes a test plan and procedures, testing tools and test cases
their expected results.
The test is conducted and all results are evaluated I, e, the test results are compared with
the expected results and concluded that software quality and reliability and acceptable.
Condition Testing:
Condition testing is a test case design method that exercises the logical condition
contained in a program module. A simple condition is a Boolean variable or a relational
expression, possibly preceded with one NOT operator. A relational expression takes the
form E 1 (Relational Operator) E 2.
Here E 1 and E2 Arithmetic expression.
Data flow testing:
The data flow testing methods selects tests paths of a program according to the location
of definitions and uses of variables in the programs. Data flow testing strategies are
useful for selecting test paths of a program containing nested if and loop statements.
For Data flow- based criteria, a definition used graph for the program is first constructed
from the control flow graph of the program. A statement in a node in the flow graph
representing a block of code has variable occurrences in it.
Loop Testing:-
Loops are cornerstone for the vast majority of all algorithms implemented in software.
And yet be often paying them little heed while conducting testing. Loop testing is a white
box testing technique that focuses exclusively on the validity look constructs.
SECURITY TESTING:-
During this testing, the tester plays the role of the individual who desires to penetrate the
system. The tester may attempts to acquire password through external clerical means and
may attack the system with custom software designed to break down and defenses that
have been constructed.
The tester may also over view the system there by denying service to others and may
purposely cause system errors to the penetrate during recovery and may browse through
insecure data, hopping to the find the key to system entry.
Maintenance
Once the software is delivered and deployed, it enters the maintenance phase. All systems
need maintenance, but for other systems it is largely due to problems that are introduced
due to aging, software needs to be maintained not because some of its components wear
out and need to be replaced, but because there are often some residual errors remaining in
the system that must be removed as they discovered.
It is commonly believed that the state of the art today is such that almost all software that
is developed as residual errors, or bugs, in them. Many of these surface only after the
system has been in operation some times or a long time. These errors, once discovered
need to be removed, leading to the software getting changed. This is sometimes called
corrective maintenance. Even without bugs, project frequently under goes change the
main reason is that project often must be upgraded and enhanced to include more features
and provide more services. This also requires modification of the project. It has been
argued that once a project system is deployed, the environment in which it operates
changes.
Hence, the needs that initiated the project development also change to reflect the needs of
the new environment. The changed project than changes the environment, which intense
requires further change. Maintenance due to this phenomenon is sometime called
adaptive maintenance.
Though maintenance is not considered a part of project development it is an extremely
important activity in the life of the software project. Thus, maintenance involves
understanding the effects of changed, because often during development, the needs of the
maintainers are not kept in mind, few support documents are produced during
development to help the maintainer the complexity of the maintenance task, coupled with
the neglect of maintenance concerns during development, makes maintenance the most
costly activity in the life of software service. The development of the project starts with
the requirements documents, which is also used to determine eventually whether or not
the delivered project is acceptable. It is therefore important that the requirement
specification contains no errors and specifies the client’s requirements correctly. It is
extremely desirable to detect errors in the requirements before the design the
development of the software begin. Let us consider the type of the errors that typically
occur in a SRS system Requirement Specification). Many different types of errors are
possible, in the requirement specification phase. But the most common errors that occurs
can be classified as four types : Omission, Inconsistency, Incorrect fact, and Ambiguity.
Input design are aimed at reducing the chance of mistakes or errors during data entry.
However an analyst must always assume that errors will occur. They must be found
during input and corrected prior to storing or processing the data. Infect, erroneous data
are frequently forgotten about until someone using a report based on those data questions
their accuracy and validity.
The general term given to methods aimed at detecting errors in input is INPUT
VALIDATION. Three main categories of methods are concerned in this project for
checking the validity. These methods are, checking the transactions, checking. The
transaction data and modifying the transaction data.
Checking the transaction:-
First and foremost, it is essential to iderify any transaction that are not valid, that is not
acceptable. Transaction can be invalid because they are incomplete, unauthorized or even
out of order. The main point which are considered in checking the validity of the
transaction in the project are.
Batch control :-
In batch environment, the occurrence of a trasactoin
And the time data about them are processed. As the proposed project is concerned about
keeping the record of all kinds of this project collection. So, there is no consideration
that how much delay is about the concerned service and sometimes the delay is
acceptable to the users.
When transaction are accumulated and not processed as they are occurring, there are very
few chances that some entries will be misplaced, forgotten or simply over looked because
keeping record of the CD’s and cassettes is a daily in a and in the proposed system
separate tables are considered for keeping the records of the each service.
Transaction validation :-
Sometime, user often attempt to process data in unaccepted ways, eater accidentally or
intentionally. So in the concerned project several validation procedures are specified that
test the acceptability of transaction.
Sequence test:-
Sequence tests use codes in the data, serial numbers to test for either of the two different
conditions ,depending on the characteristics of the application . in some system, the order
of transaction in an important when processing to the services of the collection
important to ensure that each service is processed in the order in which it arrived.
If the sequence of services record of any service is mistakenly processed before the repot
of other service that actually occurred first. There is little point in accepting input that is
missing some items of data, since the result is storage of incomplete and erroneous
information therefore input validation checks on each transaction should be made to
ensure that all essential data are included. Completeness tests are one more way of
validating the transaction in the concerned project. To ensure it is accurate and acceptable
before any data is accepted into the system for further processing or storage.
After making an in depth analysis of the problems and considering the various
requirements the project is planned to be complete in one and a half month. For
completing the project waterfall model is selected. The waterfall model has four phases
namely requirement analysis, design, coding, testing and maintenance. Thus different
activities and the milestones in the system according to the waterfall model are following
Activities
Requirement Gathering: In this phase all the requirements for developing the
software are arranged and analyzed. This phase will require problem definition,
requirement specification, software and hardware requirements etc.
Design: After analyzing the requirements the system is designed. This phase
includes logical design, physical design, database design and the interface design
of the system.
Coding: After designing the system the software is to be coded in any specific
language for this purpose visual basic is chosen as the desired front end.
Testing: After coding the system various test cases are to be developed so that the
system can be thoroughly tested and any default in the system will be reduced.
For this purpose unit testing is planned to be use.
Maintenance: after going through above phases the system will be changed
according to the feed back of different user. After that the system will be modified
or updated Finally the system will be put into work.
Milestone
The below chart explains the tasks vs. the time they will take to complete
Analysis
Design
Test Cases
Coding
Testing
Build
Software and Hardware Requirements
For software development very first and essential requirement is the availability of
software and hardware.
SOFTWARE REQUIREMENTS
Here Visual Basic will be used as front end software and Oracle 8 will be used as
backend (to store database)
HARDWARE REQUIREMENTS
IBM Compatible PC
128 MB RAM For Installing Oracle And Visual Basic
10 GB Of Hard Disk
Monochrome 15" Monitor
Writable CD ROM For Backup
132 Character 80 Cps Printer
These are the minimum requirement for working on this project, higher the hardware and
software configuration will give the best quality of software.
REFERENCES
ProgressBar1.Value = ProgressBar1.Value + 5
End If
main.Show
Unload Me
End If
End Sub
CODING OF MODULE FILE
End Sub