Project Report

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 13

INTRODUCTON

SYSTEM CONFIGURATION

HARDWARE

SOFTWARE
SYSTEM ANALYSIS
System Analysis is a process of understanding the system requirements and its
environment. It is one of the initial stages of the software development life cycle.
System analysis is the process of breaking the system down into its individual
components and understanding how each component interacts with the other
components to accomplish the system’s overall goal. System Analysis focuses on
the needs of the user, the current system, and the business processes that the
system must support. In this process, the analyst collects the requirements of the
system and documents them.

 It is the study of the existing system to identify the problem areas.


 It is a process of understanding the system requirements and its
environment.
 It involves gathering and understanding the user’s requirements.
 It involves analyzing the system in terms of its current and future needs.

1. Existing system
1) Proposed system
SYSTEM DESIGN & DEVELOPMENT
System design is an art of defining the architecture, components, modules,
interfaces and data for a system to satisfy specified requirements. It can be
considered as the application of system theory to product development. There is a
synergy with the disciplines of system analysis, system architecture and system
engineering. System design builds information gathered during the system
analysis.

It deals with transforming the customer requirements into a form that is


implemented using a programming language. This is the phase in which, the
detailed design of the system is accomplished and the user oriented performance
specification converted into a technical design specification. During this phase,
decision about overall architecture was taken. The system organized into
subsystem based on the analysis structure. A personal computer with ordinary
specification was chosen for the implementation of the design. The major activities
include general system design, design of all outputs, input design and the design of
the database.
INPUT DESIGN

An input design is the link between the information system and the user. It
comprises developing specification and procedures for data preparation and those
steps that are necessary to put transaction data into a usable form for processing
data entry.

OUTPUT DESIGN

In the output design, emphasis is given on producing a hardcopy of the information


required as the output on the screen in some predefined manner. Computer output
is the most important and direct source of the information to use.

DATABASE DESIGN

Database design is the process of producing a detailed data model of a database.


The term database design can be used to describe many different parts of the
design of an overall database system. Principally, and most correctly, it can be
thought of as the logical design of the base data structures used to store the data. In
the relational model these are the tables and views. In an object database the
entities and relationships map directly to object classes and named relationships.
However, the term database design could also be used to apply to the overall
process of designing.
DFD

ER

TABLE DESIGN
SYSTEM TESTING
System testing is the evaluation of software item to detect difference between
given input and expected output. Also to assess the feature of software
item .Testing assesses the quality of the product. Software Testing is the process
that should be done during the development process. It offers the greatest security
since the old system can take over the errors is found or inability to handle certain
type of transactions while using the new system. So testing is vital to the success of
new system. Series of the system are performed for the proposed system before the
system is ready for user acceptance. In other word software testing is a verification
and validation process.

TESTING APPROACH
The major testing strategies are:

1. Unit Testing
2. Integration Testing
3. System Testing
4. Acceptance Testing

1 Unit Testing
Unit Testing is a level of software testing where individual units/ components of
the software are tested. The purpose is to validate that each unit of the software performs
as designed. A unit is the smallest testable part of the software. It usually has one or a few
inputs and usually a single output. In procedural programming, a unit may be an
individual program, function, procedure, etc. In object-oriented programming, the
smallest unit is a method which may belong to a base/ super class, abstract class or
derived/ child class. (Some treat a module of an application as a unit. This is to be
discouraged as there will probably be many individual units within that module.)

Once all of the units in a program have been found to be working in the most
efficient and error-free manner possible, larger components of the program can be
evaluated by means of integration testing.

2 Integration Testing
The purpose of integration testing is to verify functional, performance, and
reliability requirements placed on major design items. These "design items", i.e.,
assemblages (or groups of units), are exercised through their interfaces using black
box testing, success and error cases being simulated via appropriate parameter and
data inputs. Simulated usage of shared data areas and inter process communication
is tested and individual subsystems are exercised through their input interface.
Some different types of integration testing are a big bang, top-down, and
bottom-up, mixed (sandwich) and risky hardest. Other Integration Patterns [2]
are
collaboration integration, backbone integration, and layer. Integration, client-server
integration, distributed services integration, and high-frequency integration.
Upon completion of unit testing, the units or modules are to be integrated
which gives rise to integration testing. The purpose of integration testing is to
verify the functional, performance, and reliability between the modules that are
integrated.

3. System Testing
System testing is performed on the basis of written test cases according to
information collected from detailed architecture/design document, module
specification, and requirement specification. System testing may be started
once unit, component, and integration testing are completed.

 WHITE BOX TESTING


White Box Testing (also known as Clear Box Testing, Open Box
Testing, Glass Box Testing, Transparent Box Testing, Code Based Testing or
Structural Testing) is a software testing method in which the internal structure/
design/ implementation of the item being tested is known to the tester. The
tester chooses inputs to exercise paths through the code and determines the
appropriate outputs. Programming knows how and the implementation
knowledge is essential. White box testing is testing beyond the user interface
and into the nitty-gritty of a system. This method is named so because the
software program, in the eyes of the tester, is like a white/ transparent box;
inside which one clearly sees.

 BLACK BOX TESTING


Black Box Testing, also known as Behavioral Testing, is a software testing
method in which the internal structure/ design/ implementation of the item being
tested is not known to the tester. These tests can be functional or nonfunctional,
though usually functional. This method is named so because the software program,
in the eyes of the tester, is like a black box; inside which one cannot see.

4. Acceptance Testing
Acceptance Testing is a method of software testing where a system is tested for
acceptability. The major aim of this test is to evaluate the compliance of the
system with the business requirements and assess whether it is acceptable for
delivery or not. 

Usually, black box testing method is used in acceptance testing. Testing does not
normally follow a strict procedure and is not scripted but is rather ad-hoc.
Acceptance Testing is a testing technique performed to determine whether or not
the software system has met the requirements specifications. It is the last phase of
software testing performed after System Testing and before making the system
available for actual use. 
SYSTEM IMPLEMENTATION
Front end, backend, DB
SYSTEM MAINTENANCE
Once the software is fully developed and implemented, the company starts to use
the software. The company also grows, and more divisions can be attached to the
company, or the database of the company can grow. So, after some time the
software, which has been installed, needs some modification. If the software needs
modification all the steps needed to develop new software must be executed.

Maintenance can be classified as corrective, adaptive, perfective and preventive.

1. CORRECTIVE MAINTENANCE :

It is concerned with fixing errors that are observed when the software is in use. It
deals with repair of faults or defects found in day-today system functions. The
approach in corrective maintenance is to locate the original specifications in order
to determine what the system was originally designed to do. It accounts for 20% of
all the maintenance activities.
2. ADAPTIVE MAINTENANCE :

It is the modification of software to keep it usable after a change to its operating


environment. Many factors can change an application’s environment, including
new technical knowledge, hardware and security threats. These changes occur with
greater frequency in most environments, so software that doesn’t receive regular
adaptive maintenance quickly becomes outdated. It accounts for 25% of all the
maintenance activities.

3. PERFECTIVE MAINTENANCE :

It deals with implementing new or changed user requirements. This involves


making functional enhancements to the system in addition to the activities to
increase the system performance even when the changes have not been suggested
by faults. This includes enhancing both function and efficiency of code and
changing the functionalities of the system as per user’s changing needs. It accounts
for 50%, the largest of all maintenance activities.

4. PREVENTIVE MAINTENANCE :

It involves performing activities to prevent the occurrence of errors. It tends to


reduce the software complexity thereby improving program understandability and
increasing software maintainability. It comprises documentation updating, code
optimization and code restructuring. This is limited to the maintenance
organization only and no external requests are acquired for this type of
maintenance. It accounts for 5% of all the maintenance activities.
SCOPE

CONCLUSION

BIBLIOGRAPHY

APPENDIX

You might also like