ASSIGNMENT MANAGEMENT SYSTEM PROJECT REPORT
TABLE OF CONTENTS
Contents
at a Glance
Ø Introduction
·
About
Company . . . . . . . . . . . . . . . .
. . . . . .
·
Abut Project . . . . . . . . . . . . . . . . . . . . . …
Ø Project Analysis
·
Feasibility Study . . . . . . . . . . . . . .
. . . .
ü Economical
ü Technical (H/W & S/W
Specification)
ü Operational
·
Requirements Analysis . . . . . . . . . . . . .
Ø Project Design
·
Workflow Diagram . . . . . . . . . . . . . . . . . . .
ü DFDs
ü Flow Chart
ü E-R Diagram
Ø Database Design
Tables
Ø Testing
Ø Snapshots
Ø Conclusion
Ø Reference
OUTLINE OF PROJECT
Project title: Assignment
Management System
Objective:
Now a days in many company to assign job to employee they call a meeting and to trace the progress report of work also they meet directly then question arises to do that work on line they want a system in which they are able to give job online and trace the current status of the work and completion according to that. They also major the employee efficiency regarding the work completion on time.
The main objective of this software is to automate the assignment process of work. Using this software an employee can perform assignment related work online. The AMS software will be used by the employees of the HCL at the time of their assigning of work and thereafter. AMS is designed to manage, assigning of work process entirely online .It is flexible enough to co-operate any changes or enhancements made later within the application.
FEASIBILITY STUDY - ASSIGNMENT MANAGEMENT SYSTEM PROJECT
A feasibility study is an
evaluation of a proposal designed to determine the difficulty in carrying out a
designated task. Generally, a feasibility study precedes technical development
and project implementation.
·
Technology and system feasibility:
The assessment is based on an outline design of system requirements in
terms of Input, Processes, Output, Fields, Programs, and Procedures. This can
be quantified in terms of volumes of data, trends, frequency of updating, etc.
in order to estimate whether the new system will perform adequately or not.
Technological feasibility is carried out basically to determine whether the
company has the capability in terms of software, hardware, personnel and
expertise to handle the completion of the project.HCL fulfilled all the above
requirements for the efficient working of web application.
·
Economic
feasibility:
Economic analysis is the most frequently used method for evaluating the
effectiveness of a new system. More commonly known as cost/benefit analysis,
the procedure is to determine the benefits and savings that are expected from a
candidate system and compare them with costs. If benefits outweigh costs, then
the decision is made to design and implement the system. An entrepreneur must
accurately weigh the cost versus benefits before taking an action.
o Cost
Based Study: It is
important to identify cost and benefit factors. Cost and benefits can be
categorized into the following categories. Basically it is an analysis of the
costs to be incurred in the system and benefits derivable out of the system. In
a broad sense the costs can be divided into two types 1. Development costs 2.
Operating costs.
o Time
Based Study: Contrast to
the traditional system management it can generate any information of data just by single click and it saves user time
.No extra time is being provided to deliver application.
·
Operational
feasibility:
It is a measure of how well a proposed system solves the problems, and
takes advantages of the opportunities identified during scope definition and
how it satisfies the requirements identified in the requirements analysis phase
of system development. This project provide interactive interface to generate
report as per the requirements and also user can update the information
efficiently. Most of the staff in NIC is computer literate hence the user would
be able to use the system. Further NIC also have trained manpower who can keep
the system operational and upgrade it if needs arises.
REQUIREMENT ANALYSIS - ASSIGNMENT MANAGEMENT SYSTEM PROJECT
Requirement Analysis is the
first phase of software development process. This phase focuses to understand
the problem Requirement Analysis is on identifying what is need from these
systems, not how the system will achieve its goals. In this phase often at
least two parties are involved in Software Development-a client and a
developer. The developer has to develop the system to satisfy the clients’
needs. The developer and client arrange a meeting and discuss his/her own views
the developer asks the clients for needs. After a meeting the developer
understands what the requirements of the client are. Before start the development
process, the developer analyze, test the requirements which are given by the
clients. According to those requirements the developer starts development
process. Hence the developer needs a user’s problem.
In the software requirement we are dealing
with the requirements of the proposed system, that’s the capabilities of that
system, which is yet to be developed, should have. The software requirement
specification (SRS) is a document that completely describes what the proposed
software should do without describing how the software will do it. So the basic
goal of Requirement Phase is to produce the SRS, which describes the complete
external behavior of the proposed software.
The basic aim of problem
analysis is to obtain the clear understanding of the needs of the clients and
the user, what exactly described from the software, and what the constraints on
the solution are? This involves a meeting of user and developers. The developer
may ask the following questions to users-:
.Who will use the developed
software?
.What types of
characteristics may have the software?
.What is the fundamental
requirements?
In the Base Online Courier Management System
there are different types of Users. Every user has a unique ID.
a) Functional Requirements:
In the development process of the software
must face the new record should have a unique registration number.
The software should have the capability that it can be used by the authorized user
following requirements-:
b) User requirements:
The main requirement of the user is that
this system should be used by the Users and administrator for proper
maintaining.
The developer can face a number of requirements
given by the user. So, the software should have a number of facilities. The
user may require the followings-:
(i) Correctness:
Correctness is the degree
to which the software performs its required function. The extent to which the
software satisfies its specifications and fulfills the customer’s mission
objectives.
The software must be correct. The software is
correct if the software is tested in each step of its development.
A developed software can said to be correct if
it fulfills the user’s requirement. This software must operate correctly to its
user .The correctness of the software is measured on the basis of the required
information.
ii) Performance:
The software must perform
required action. All the requirements of the software directly related to its
performance. The performance of the software is measured on the basis of
response time taken to display the record of the Author. The software response
is measured on the basis of execution of the program constraints.
In the Performance, the
software must be able to “process all the operations quickly”. So the
performance is measured by throughput, efficiency, response time and the
processing speed.
(iii) User Friendly:
The developed software must
be user friendly by which the user can understand the software easily. If the
software provides a good interface then it is said to be user friendly. If
software is developed in GUI rather than CUI, then the developed software is
friendlier.
The Base of Courier Management System is
developed by using the ASP.Net as a user interface and the background using Sql.
The software can be handled easily and user can use it without more knowledge
about the computer. The software provides integrated and consistent
information.
(iv) Maintenance:
The user wants that the
software must be maintained properly before accepting the software. Software
needs to be maintained not because some of its components wear out and need to
be replaced, but because there are often same residual errors remaining in the
system that must be removed as they are discovered.
The Maintenance of the
software is measured by using the maintainability. The maintainability is ease
with which a program can be corrected, if an error is encountered. The
maintenance depends on the user’s requirement because there are many kind of
maintenance.
Thus, the user requires
maintenance because, maintenance involves understanding the software (code and
related modules), understanding the effects of change, making new change.
Because often during development some needs are not kept in mind.
C) Performance RequirementS
User-Friendly
The system
should be user-friendly so that the user without any difficulty can easily
understand
it.
Functionality
The system
should provide functions, which can meet the stated, and theimplied needs
of the end
user.
Maintainability
The system
should be easy to maintain i.e. it should have the capability to
bemodified,
modification include corrections, improvements or adoption
of
Software according to changed environments and requirements.
b)
Less time consuming
c) The system should utilize time
effectively.
Portability
The system
portability should be taken care of without any interventions.
Portability means the capability of the
software to be transferred from one
environment to another.
Security
The
system should be secured from unauthorized access and should be password
protected so that no other user can access
it.
Error tolerance
The
system should be able handle the user errors in any case.
EFFICIENCY
The system should be
capable of providing the required performance
related to the amount of resources of the
organization.
RELIABILITY
The system should be capable enough to
maintain the level of
performance.
Hardware Requirements
Server
side Hardware Requirement:
Ø AMD
Athlon 64 with processor speed 2.8 or more
Ø 256
DDR Ram
Ø 40
GB Hard disk
Ø Network
Interface card
Ø IIS
Ø CD-Drive
Server side Software
Requirement
Ø Windows
XP Professional
Ø Visual
studio 2008 IDE
Ø SQL
Server 2005
Client
side Hardware requirements:
Ø Processor Dual core based
computer
Ø 2
GB RAM
Ø 20
GB HDD
Ø 100
Mbps LAN
Ø Web
Browser
To develop this project the various Software resources
are used.
- Front End :
ASP
- Back End :
SQL server 2005
- Web Server : IIS
- Technology : .net technology
- Code-Behind Language : JavaScript, HTML,CSS
- IDE :
visual studio 2005
INTRODUCTION TO PROJECT DESIGN - ASSIGNMENT MANAGEMENT SYSTEM PROJECT
System design is a solution of “how to” approach to
the creation of the proposed system. It facilitates and provides the procedural
detail necessary for implementation of the system recommended in the Initial
study and Feasibility study. Emphasis is given on translating the requirements
into design specification. System design is a highly creative process. This
System design process is also referred as data modelling. The most common
format used for data modelling is entity-relationship (E-R) diagramming. Data
modelling using the E-R notation explains the characteristics and structure of
data independent of how the data may be stored in computer memories.
The
design of the system is essentially a blueprint or a plan for the solution for
the system. Here we 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. A component of a system
can be considered a system with its own components. In a software system a
component is a software module.
Modules
The user
classes can be divided into three categories..
1.Admin
2.Super user
3.General
user
Admin:- Admin user is a power user having the capability to create a new
super user as well as general user and also delete the super usre and general
user. This user also having the power to assign the assignment to the super
user.
Super
User:- super user is a power user having the capability to assign the
assignment to general user. This user also having the power to add and delete
the assignment.
General
User:-General user can see the details of the assignment.and download
the assignment from the database and can see the list of assignment and also
can change the own password.
TESTING - ASSIGNMENT MANAGEMENT SYSTEM PROJECT
INTRODUCTION
No program
or system design is perfect; communication between the user and the designer is
not always complete or clear, and time is usually short. The result is errors
and more errors. The number and nature of errors in a new design depend on
several factors: Communication between the user and the designer i.e. the
programmer’s ability to generate a code that reflects exactly the system
specification and the time frame for the design.
Theoretically,
a new designed system should have all the pieces in working order, but in
reality, each piece works independently. Now is the time to put all the pieces
into one system and test it to determine whether it meets the requirements of
the user.
Levels of Testing
1. Unit Testing
Unit testing is a procedure used to verify that a particular segment of
source code is working properly. The
idea about unit tests is to write test cases for all functions or methods. Ideally, each test case is separate from the
others. Unit testing focuses
verification efforts on the smallest unit of software design, the software
component or module. Using the component
level design description as a guide, important control paths are tested to
uncover errors within the boundary of the module. The relative complexity of test and uncovered
errors is limited by the constraints scope established for unit testing. The
unit test is white box oriented, and the step can be conducted in parallel for
multiple components. In this project many aspects are covered under unit
testing, because if any of the function does not work properly then system may
be fail.
2. Integrated testing
Integrated testing
is a systematic technique for construction of the whole program structure whole
at the same time conduction tests to uncover errors associated with
interfacing. The objective is to take
unit tested components and build a program structure that has been dictated by
design. Integrated testing follows unit testing and precedes system
testing. Integration testing takes as
its input, modules that have been checked out by unit testing, groups them in
larger aggregates, applies tests defined in an integration test plan to those
aggregates, and delivers as its output, the integrated system ready for system
testing. The purpose of Integration
testing is to verify functional performance and reliability requirements placed
on major design items.
3 .System
Testing
System
testing is executing a program to check logic changes made in it and with the
intention of finding errors-making the program fail. Effective testing does not
guarantee reliability. Reliability is a design consideration.
4 . Acceptance Testing
Acceptance
testing is conducted by a customer to verify that the system meets the
acceptance criteria of the requested application. It generally involves running
a suite of tests on the completed system. Each individual test, known as a
case, exercises a particular operating condition of the user's environment or
feature of the system, and will result in a pass or fail boolean outcome. There
is generally no degree of success or failure.
4.1
Alpha Testing
Alpha testing is an actual operational
testing done by potential users/customers or an independent test team at the
developers' site, but outside the development organization. In other words,
alpha testing is a type of acceptance testing carried out at developer’s site
by users (internal staff). In this type of testing, the user goes on testing
the system and the outcome is noted and observed by the developer
simultaneously.
4.2 Beta Testing
Beta
testing
comes after alpha testing. Beta testing is considered the second phase of
software testing. Beta tests are typically external tests to identify any
performances issues or bugs prior to an official release. Beta tests can be
open or closed. A closed beta test is used to control the number of users
participating. An open test is open to anyone who has an interest in beta testing.
Beta testers
are important because it is almost impossible for developers to test their
software in all of the various conditions that might occur. Software should
never be released without thorough beta testing. It is impossible to predict or
test software on all kinds of hardware with other applications. Some developers
segment the closed beta into different release stages so they can maximize
feedback. Historically the majority of feedback is received from beta testers
within the first week of the beta release.
Testing Methodology
1. Black Box Testing
Black-box test design treats the system as a "black-box", so it doesn't explicitly use knowledge of the internal structure. Black-box test design is usually described as focusing on testing functional requirements. Majority of the application are tested by black box testing method. We need to cover majority of test cases so that most of the bugs will get discovered by black box testing. Test cases can be designed as soon as the functional specifications are complete.
Following test cases are applied in the AMS:
o Check whether users enter the correct username and password and accordingly provide the facility.
2. White Box Testing
White box testing strategy
deals with the internal logic and structure of the code. White box testing is
also called as glass, structural, open box or clear box testing. The tests
written based on the white box testing strategy incorporate coverage of the
code written, branches, paths, statements and internal logic of the code etc.
In order to implement white box testing, the tester has to deal with the code
and hence is needed to possess knowledge of coding and logic i.e. internal
working of the code. White box test also needs the tester to look into the code
and find out which unit/statement/chunk of the code is malfunctioning.
Basic tests done in white box testing are
o
Defining the data and control flow in the program
o
Uniform
representation of the program, language independent
o
Simple basic
elements: assignment and condition
o
Statement: each statement executed at least once
o
Branch: each branch traversed (and every entry point
taken) at least once Branch Coverage
requires that each branch will have been traversed, and that every program
entry point will have been taken, at least once.
o
Condition: each condition True at least once and False
at least once
o
Branch/Condition: both Branch and Condition coverage achieved
o
Compound
Condition: all combinations of condition
values at every branch statement covered (and every entry point taken). It also
known as Multiple Condition
Coverage.
o
Path: all program paths traversed at least once
o
Every program entry
point will have been taken, at least once.
o
Loop Coverage requires that the body of loops be executed 0, 1, 2, t,
max, and max+1 times, where possible.
No comments:
Post a Comment