You are on page 1of 14

Web Application Project

Specifications
for

Web Programming Lab

Version 1.0 approved

Prepared by RASHMI R

DEPT. OF ISE, RVCE

12 NOVEMBER 2010

Dept. of ISE, RVCE Page i


Web Programming Mini Project Report Template 2010

1. Introduction

1.1 Purpose

<Identify the product whose software requirements are specified in next chapter, describe the
need for development of the product. State Very abstractly what the system does to fulfill the
needs of the end user. >

1.2 Motivation

<Describe the rationale behind development of the project and selection of the theme of
project.eg. tell about what inspired you to select the topic. And what is the idea.>

1.3 Project Scope

<Provide a short description of the software being specified and its purpose, including relevant
benefits, objectives, and goals. Relate the software to corporate goals or business strategies.
specify the role the project would have after implementation. The possibility of using the project
in solving real world problem eg. Understanding the practical design and implementation issues
of web applications, consolidating various web technologies and integrate these to develop
innovative Rich internet application>

1.4 Literature survey

< After selecting the a relevant topic (project theme), review information from various sources
(books, journals, conference proceedings, web sites, product literature, etc.), and formulate a
coherent report about that topic. Add reference numbers wherever relevant.>

2. Overall Description
Provide the product perspective here. <Describe the context and origin of the product being
specified in this SRS. For example, state whether this product is a follow-on member of a product
family, a replacement for certain existing systems, or a new, self-contained product.>

2.1 Product Features

<Summarize the major features the product contains or the significant functions that it performs or
lets the user perform. Details will be provided in Section 2.3, so only a high level summary is
needed here. Organize the functions to make them understandable to any reader of the SRS.

Dept. of ISE, RVCE Page 1


Web Programming Mini Project Report Template 2010

2.1.1 Functionality Requirements


<Itemize the detailed functional requirements associated with every product feature. These
are the software capabilities that must be present in order for the user to carry out the
services provided by the feature, or to execute the use case. Include how the product
should respond to anticipated error conditions or invalid inputs. Requirements should be
concise, complete, unambiguous, verifiable, and necessary. Use “TBD” as a placeholder to
indicate when necessary information is not yet available.>

<Each requirement should be uniquely identified with a sequence number or a


meaningful tag of some kind.>

REQ-1:

Example: functional requirements to Submit Request for Proposal to Suppliers

REQ-1: Select suppliers to whom the RFP(REQUEST PROPOSAL) will be submitted. These
suppliers should be on the list of qualified suppliers. If they are not, there should be some evidence that
they would be appropriate candidates for performing the work to be subcontracted. See Appendix H,
Guidance for Selecting Suppliers.
REQ-2: Contact suppliers to determine whether they wish to receive the RFP. If so, identify the
individual at the supplier’s site to whom the RFP is to be submitted.
REQ-3: If necessary, execute a nondisclosure agreement with suppliers who wish to receive the RFP.
REQ-4: Deliver the RFP to the suppliers by the most expeditious route, confirming receipt by each
supplier.
REQ-5: Record the list of suppliers to whom the RFP was submitted in the proposal evaluation report.
REQ-6: Respond to questions submitted by suppliers. Communicate clarifications or
corrections concurrently to all suppliers who received the RFP. Revise the RFP as necessary
according to the project’s change control process.

2.2 Operating Environment

<Describe the environment in which the software will operate, including the hardware platform,
operating system and versions, and any other software components or applications with which it
must peacefully coexist.>

2.3 External Interface Requirements

2.3.1 User Interfaces

<Describe the logical characteristics of each interface between the software product and the
users. This may include sample screen images, any GUI standards or product family style guides
that are to be followed, screen layout constraints, standard buttons and functions (e.g., help) that
will appear on every screen, keyboard shortcuts, error message display standards, and so on.
Define the software components for which a user interface is needed. Details of the user
interface design may be documented in a separate user interface specification(manual )
and added in appendix .>

Dept. of ISE, RVCE Page 2


Web Programming Mini Project Report Template 2010

2.3.2 Hardware Interfaces

<Describe the logical and physical characteristics of each interface between the software product
and the hardware components of the system. This may include the supported device types, the
nature of the data and control interactions between the software and the hardware, and
communication protocols to be used.>

2.3.3 Software Interfaces

<Describe the connections between this product and other specific software components (name
and version), including databases, operating systems, tools, libraries, and integrated commercial
components. Identify the data items or messages coming into the system and going out and
describe the purpose of each. Describe the services needed and the nature of communications.
Refer to documents that describe detailed application programming interface protocols. Identify
data that will be shared across software components. If the data sharing mechanism must be
implemented in a specific way (for example, use of a global data area in a multitasking operating
system), specify this as an implementation constraint.>

DBI

2.3.4 Communications Interfaces

<Describe the requirements associated with any communications functions required by this
product, including e-mail, web browser, network server communications protocols, electronic
forms, and so on. Define any pertinent message formatting. Identify any communication
standards that will be used, such as FTP or HTTP. Specify any communication security or
encryption issues, data transfer rates, and synchronization mechanisms.>

2.4 Other Nonfunctional Requirements

2.4.1 Performance Requirements

<If there are performance requirements for the product under various circumstances, state them
here and explain their rationale, to help the developers understand the intent and make suitable
design choices. Specify the timing relationships for real time systems. Make such requirements
as specific as possible. You may need to state performance requirements for individual functional
requirements or features.>
Reference :BEST PRACTICE TO IMPROVE PERFORMANCE:http://developer.yahoo.com/performance/rules.html

2.4.2 Safety Requirements

<Specify those requirements that are concerned with possible loss, damage, or harm that could
result from the use of the product. Define any safeguards or actions that must be taken, as well
as actions that must be prevented. Refer to any external policies or regulations that state safety
issues that affect the product’s design or use. Define any safety certifications that must be
satisfied.>

Dept. of ISE, RVCE Page 3


Web Programming Mini Project Report Template 2010

HINT
TAKING BACKUP

2.4.3 Security Requirements

<Specify any requirements regarding security or privacy issues surrounding use of the product or
protection of the data used or created by the product. Define any user identity authentication
requirements. Refer to any external policies or regulations containing security issues that affect
the product. Define any security or privacy certifications that must be satisfied.>

ENCRYPTION
AUTHENTICATION
AUTHORIZATION

2.4.4 Software Quality Attributes

<Specify any additional quality characteristics for the product that will be important to either the
customers or the developers. Some to consider are: adaptability, availability, correctness,
flexibility, interoperability, maintainability, portability, reliability, reusability, robustness, testability,
and usability. Write these to be specific, quantitative, and verifiable when possible. At the least,
clarify the relative preferences for various attributes, such as ease of use over ease of learning.>

Portability

3. Design

3.1 Design and Implementation Constraints

<Describe any items or issues that will limit the options available to the developers. These might
include: corporate or regulatory policies; hardware limitations (timing requirements, memory
requirements); interfaces to other applications; specific technologies, tools, and databases to be
used; parallel operations; language requirements; communications protocols; security
considerations; design conventions or programming standards (for example, if the customer’s
organization will be responsible for maintaining the delivered software).>

Hints

The presentation layer/ web site is designed to work efficiently on Particular browser ( either IE or
Firefox)

The Apache web server being used is not connected to the external network.

3.2 Assumptions and Dependencies

<List any assumed factors (as opposed to known facts) that could affect the requirements stated
in the SRS. These could include third-party or commercial components that you plan to use,

Dept. of ISE, RVCE Page 4


Web Programming Mini Project Report Template 2010

issues around the development or operating environment, or constraints. The project could be
affected if these assumptions are incorrect, are not shared, or change. Also identify any
dependencies the project has on external factors, such as software components that you intend
to reuse from another project, unless they are already documented elsewhere (for example, in the
vision and scope document or the project plan).>

Tables are created in MYSQL

Web browser compatible with the versions used.


Plugins used.

3.3 System Architecture

<This section should provide a high-level overview of how the functionality and responsibilities of
the system were partitioned and then assigned to subsystems or components. Don't go into too much
detail about the individual components themselves (there is a subsequent section for detailed
component descriptions). The main purpose here is to gain a general understanding of how and why
the system was decomposed, and how the individual parts work together to provide the desired
functionality.>

Write architecture diagram - A simple diagram that shows the major components of the overall
system, subsystem interconnections, and external interfaces.
Reference:
http://support.novell.com/techcenter/articles/nc2000_09a.html

http://www.ibm.com/developerworks/ibm/library/it-booch_web/

http://www.15seconds.com/issue/011023.htm

http://www.exforsys.com/tutorials/client-server/n-tier-client-server-architecture.html

VERY ABSTRACT DIAGRAM.


MODULES IN CLIENT SERVER DATABASE ARE NOT TO BE SHOWN

DIAGRAM START FROM LEFT TO RIGHT:

CLIENT ______________INTERFACE_______SERVER_______INTERFACE________DATABASE

Label the interface (lines).

Dept. of ISE, RVCE Page 5


Web Programming Mini Project Report Template 2010

4. Detailed Design

4.1 Web Diagram/Process Flow Chart

<Describe all important modules in client and server side. Elaborate the architecture diagram to
depict navigation of web pages, mapping of request document with specific server side
program.>

Web diagram

Reference:
http://publib.boulder.ibm.com/infocenter/radhelp/v6r0m1/index.jsp?topic=
%2Fcom.ibm.etools.web.diagram.doc%2Ftopics%2Fcwebdia003.html

or

write Process flow diag as below:


Ref: http://www.ibm.com/developerworks/rational/library/06/0124_hu/

Figure 27. Sample process flow diagram for a web-based J2EE application

Process details can be written in few lines following the diagram.

Dept. of ISE, RVCE Page 6


Web Programming Mini Project Report Template 2010

ELABORATE THE SYSTEM ARCHITECTURE . SPECIFY THE MODULES IN CLIENT, SERVER


AND DATABASE IN LEFT TO RIGHT ORDER(DATABASE SHOULD BE TO THE RIGHT OF
DIAGRAM).

4.2 Detailed Description of Modules

<List the modules (for example, Login, invoice ,etc. )>

4.2.1 Module 1: <name>

<This section should provide detailed description of what module does. >

Write Flow chart – to represent the flow clearly.

4.2.2 Module 2: <name>

<This section should provide detailed description of what module does. >

Write Flow chart – to represent the flow clearly.

So on……………………

Dept. of ISE, RVCE Page 7


Web Programming Mini Project Report Template 2010

5. Implementation

5.1 Platform

<Describe the platform on which the project will be deployed(eg. Fedora, windows etc.>

5.2 Programming Languages

<List the languages used with few characteristics of programming languages that are
implemented in the project >

5.3 Implementation of Module <name>

<implementation details with important Instructions highlighted>

5.4 Implementation of Module <name>

<implementation details with important Instructions highlighted>

So on……

WRITE ONLY SIGNIFICANT CODE USED IN YOUR PROJECT OTHER THAN WRITING
PRESENTATION LAYER AND DATABASE ACCESS.

DESCRIBE SPECIFIC BUSINESS LOGIC (highlight of the project) USED IN YOUR PROJECT

Dept. of ISE, RVCE Page 8


Web Programming Mini Project Report Template 2010

TESTING
6.1 Unit Testing
Unit testing is done to verify and validate whether individual units of source code are fit for use. A
unit is the smallest testable part of an application. The smallest unit of the Education Loan
Management System may be an insert, delete or update operation.

6.1.1 Unit Test Case1


Table 6.1 Unit Test Case1 for Education Loan Management System

Sl No. of test case : 1


Name of test : Insert test
Item / Feature being tested : Set bank details
CodeNo =’GM456’, Name = ‘Grameen Bank’, Estd_year =
Sample Input : 1975, PlotNo = 121, Street = ‘Market Road’, City = ‘Mysore’,
PinCode = 687001
Expected output : Message: Item inserted successfully
Actual output : Message: Item inserted successfully
Remarks : Test succeeded

6.1.2 Unit Test Case2


Table 6.2 Unit Test Case2 for Education Loan Management System

Sl No. of test case : 2


Name of test : Delete test
Item / Feature being tested : Delete student details
Sample Input : StudID = ‘RV123’
Expected output : Message: Item deleted successfully
Actual output : Message: Item deleted successfully
Remarks : Test succeeded

6.1.3 Unit Test Case3


Table 6.3 Unit Test Case3 for Education Loan Management System

Sl No. of test case : 3


Name of test : Update test
Item / Feature being tested : Update education loan details
Sample Input : LoanID = ‘L123’, PlanID = ‘P123’, Total_amount = 125000,
Status = ‘Cleared’, Installment = 25000
Expected output : Message: Item updated successfully
Actual output : Message: Item updated successfully

Dept. of ISE, RVCE Page 9


Web Programming Mini Project Report Template 2010

Remarks : Test succeeded


6.1.4 Unit Test Case4
Table 6.4 Unit Test Case4 for Education Loan Management System

Sl No. of test case : 4


Name of test : Validation test for entity integrity
Item / Feature being tested : Insert sales executive details
Sample Input : ExecID is NULL
Expected output : Message: Enter a value for ExecID!
Actual output : Message: Enter a value for ExecID!
Remarks : Test succeeded

6.1.5 Unit Test Case5


Table 6.5 Unit Test Case5 for Education Loan Management System

Sl No. of test case : 5


Name of test : Validation test for key integrity
Item / Feature being tested : Insert student details
Sample Input : StudID entered is same as another value in the database
Expected output : Message: The same StudID already exists!
Actual output : Message: The same StudID already exists!
Remarks : Test succeeded

6.1.6 Unit Test Case6


Table 6.6 Unit Test Case6 for Education Loan Management System

Sl No. of test case : 6


Name of test : Validation test for referential integrity
Item / Feature being tested : Insert rate plan details
Sample Input : LoanID entered does not exist in the Education_Loan table
Expected output : Message: The entered LoanID does not exist!
Actual output : Message: The entered LoanID does not exist!
Remarks : Test succeeded

6.2 Integration Testing


Integration testing (sometimes called Integration and Testing, abbreviated "I&T" is the
activity of software testing in which individual software modules are combined and tested as a
group. It occurs after unit testing and before system testing. Individual forms which had been unit
tested are integrated and then tested to check whether navigation is possible from one form to the
other in a seamless manner. Thus, the working of connectivity can be tested.

6.2.1 Integration Test Case1

Dept. of ISE, RVCE Page 10


Web Programming Mini Project Report Template 2010

Table 6.7 Integration Test Case1 for Education Loan Management System

Sl No. of test case : 1


Name of test : Form navigation
Item / Feature being tested : Login button
Sample Input : Userid=”admin” ,password=”student”
Expected output : Move to next page and other pages on successive clicks
Actual output : Move to next page and other pages on successive clicks.
Remarks : Test succeeded

6.2. 2 Integration Test Case2


Table 6.8 Integration Test Case2 for Education Loan Management System

Sl No. of test case : 2


Name of test : Crystal report
Item / Feature being tested : View student details
Sample Input : Click button
Expected output : Display student details
Actual output : Display student details
Remarks : Test succeeded

6.2. 3 Integration Test Case3


Table 6.9 Integration Test Case3 for Education Loan Management System

Sl No. of test case : 3


Name of test : Data retrieval into form
Item / Feature being tested : View bank details
Sample Input : CodeNo = ‘B123’
Expected output : Display bank details in form
Actual output : Display bank details in form
Remarks : Test succeeded

6.3 System Testing


6.3.1 System Test Case1
Table 6.10 System Test Case1 for Education Loan Management System

Sl No. of test case : 1


Name of test : Education Loan Management System
Item / Feature being tested : Dbms-sem5.sln
Sample Input : Data entered through forms
Expected output : Updated data displayed in generated reports
Actual output : Updated data displayed in generated reports
Remarks : Test succeeded

Dept. of ISE, RVCE Page 11


Web Programming Mini Project Report Template 2010

6. Results
<Describe the result of project.>

6.1 Observation

<summarize the process and results obtained. Also specify the limitations in
technology/organization/guidlines which affected the implementation/realization of the product
features >

6.2 Advantages and Limitations

<summarize the process and results obtained. Also specify the limitations in
technology/organization/guidlines which affected the implementation/realization of the product
features >

7. Conclusion
<one /two paragraph.>

7.1 Future Enhancements

<specific points >

Appendix –snapshots (few)

REFERENCE

Dept. of ISE, RVCE Page 12


Web Programming Mini Project Report Template 2010

Dept. of ISE, RVCE Page 13