2.0 Tools and Software Used - Google Code

mexicanmorningΔιαχείριση Δεδομένων

16 Δεκ 2012 (πριν από 4 χρόνια και 11 μήνες)

129 εμφανίσεις

R
EQUIREMENT
M
ANAGEMENT
S
YSTEM



Project Report




Requirement Management System, iTeam24x7 © 2008


1




Requirement
Management
System

Project Report

Priyanka Tyagi (10437649)

Bindu Madhav Krishna Miriyala (10432826)


Team: iTeam24x7

Delivarable#5 Project Report

R
EQUIREMENT
M
ANAGEMENT
S
YSTEM



Project Report




Requirement Management System, iTeam24x7 © 2008


2


Contents

1.0

GOALS ACHIEVED

................................
................................
................................
................................
...............................

3

2.0

TOOLS AND SOFTWARE U
SED

................................
................................
................................
................................
.............

4

3.0

PROBLEMS AND SOLUTIO
NS
................................
................................
................................
................................
...............

5

4.0

DISTRIBUTION OF WORK
:

................................
................................
................................
................................
...................

6

5.0

FUTURE IMPROVEMENTS

................................
................................
................................
................................
...................

8

6.0

SOURCE CODE
................................
................................
................................
................................
................................
.....

8

7.0

USER MANUAL

................................
................................
................................
................................
................................
...

8



R
EQUIREMENT
M
ANAGEMENT
S
YSTEM



Project Report




Requirement Management System, iTeam24x7 © 2008


3



SOFTWARE REQUIREMENTS SPECIFICATION DOCUMENT




1.0

Goals Achieved

TODO: Requirements Table here

R
EQUIREMENT
M
ANAGEMENT
S
YSTEM



Project Report




Requirement Management System, iTeam24x7 © 2008


4


2.0

Tools and Software Used

Tools

Eclipse: We used Eclipse IDE for development.

SVN: We used SVN versio
n control for backing up source code and its sharing.

ANT: We used ANT as build tool to build the project.

Junit: We used Junit to run the test case suite for integration testing.


Database
:

PostgreSQL 8.3: We used this open source database for our projec
t.


Web Server:
Tomcat 5.5


Technology:

Java Server Pages (JSP): We used it to develop web pages.

Java 1.6: We used it for developing back
-
end classes.

JDBC: We used it database connectivity.

JavaScript: We used it for client side scripting.

AJAX: We used

this technology for providing quick response.

Servlet: We used it to add dynamic contents to web server.

HTML: We used it for writing the web pages.

CSS: We used it for formatting the web pages.


Web browser:
Firefox 3.0.4




R
EQUIREMENT
M
ANAGEMENT
S
YSTEM



Project Report




Requirement Management System, iTeam24x7 © 2008


5


3.0

Problems and Solutions

Prob
lem1: Slow UI response

Initially the user interface response was very slow. Every time user is submitting new data, then
whole page used to reload again and again. Every time, there is a new request sent to server to load
the page again. This made the refr
esh time for a page very slow.


Solution: We needed a mechanism to ensure that if a part of web page is changed, then only that part
should get refresh. It should not send request to server to reload the whole page again. We used Ajax
for refreshing the ch
anged portion of the web page only. This made response time faster than before.


Problem2: Slow Sorting response

The second problem was associated with the sorting mechanism for the result of the search and
reports. Sending the request to server for sortin
g the given data was very costly and slow operation.


Solution: It was bandwidth consuming to send data back to server for sorting. Such kind of operations
is very slow as well. We needed a mechanism, which can sort the given data at client end only. We
a
chieved by using JavaScript library to do sorting at client’s end.


Problem3: Debugging and Problem diagnose


Solution: While developing the application, it was quite challenging to find out the cause of incorrect
functioning of the application. To diagnos
e system easily and effectively, we developed a debugging
framework. This framework prints very informative messages for every activity performed by the
system.


Problem4: Integration Testing mechanism for core classes


Solution: We needed a testing mechan
ism that can verify that any change in core classes has not
broken any kind of functionality. We achieved it by writing Junit test case suit for all java classes. We
ran this test suite at the end every major change or refactoring.


Problem5: Wedding Vacat
ion and Time constraints

We were only two members in our team. We went on vacation for our wedding for a month during
the peak time of semester. We had less time than our other classmates.


Solution: We solved this problem by working very hard day and nigh
t. We submitted our most of the
project deliverables (DSD and TSD and all evaluations) before due date.


Problem6: Geographically separated

We both team members were located at different and far off places on our internships. We could
never meet face to fa
ce for any discussion on project.


Solution: We solved this problem by using online meetings software like Go To meetings and Skype
to arrange the code review and development. We used SVN version control system to share the code
between us.




R
EQUIREMENT
M
ANAGEMENT
S
YSTEM



Project Report




Requirement Management System, iTeam24x7 © 2008


6

4.0

Distribution

of Work

Since we were two members in our team, so we have divided all responsibilities exactly 50
-
50%.

We have taken the responsibilities 2 phases each for four phases. This is explained as follows:

Phase I: Requirement Gathering Phase (RSD)

Phase II: De
sign Specification Phase (DSD)

Phase III: Testing Phase (TSD)

Phase IV: Implementation Phase (Source Code)

Phase V: Deployment (Project Demonstration, Source Code submission, User Manual and Project Final
Report)


The implementation phase doesn’t have any
specific team leader as both of the members knew their
responsibilities very well and they contributed equally. Both the team members were self
-
guided. However,
they discussed all the implementation time to time. We have not named one of us as team leader
for this
phase, because there was no communication with Professor and TA regarding coding. “Priyanka Tyagi” did
all negotiations on project requirements with Professor, as we decided her to be the point of contact for our
team through out semester.


The te
am member’s details are as follows:

a.

Details of first team member: (
Team Leader
-

Phase I + Phase II
)

i.

Name:

1.

First Name: Priyanka

2.

Last Name: Tyagi

ii.

Course: CS 487
-
3 (CRN
-

11061)


Internet (Out
-
of
-
State)

iii.

CWID: 10437649

iv.

Email:
ptyagi2@iit.edu

b.

Details of second team member: (
Team Leader
-

Phase III + Phase V
)

i.

Name:

1.

First Name: Bindu Madhav Krishna

2.

Last Name: Miriyala

ii.

Course: CS 487
-
3 (CRN
-

11061)


Internet (Out
-
of
-
State)

iii.

CWID: 1
0432826

iv.

Email:
bmiriyal@iit.edu


Activities carried out in each of the phase:


Phase I: Requirement Gathering Phase (RSD)

a.

Gathered requirement from Client (Professor)

b.

Negotiated on requirement and deliverables

c.

Defined the scope of the software in terms of r
equirement table in RSD.

d.

Documented the requirements in form of RSD.

e.

Developed the Use cases to understand the requirements visually.

f.

Developed the Domain model.

g.

Developed the Static structure of class hierarchy.

h.

Decided on the application type. We have de
cided to develop a web application.

i.

Decided on the infrastructure and architectural framework. We decided on using three
-
tier
architecture.

j.

Decided on database to be used for data storage. We have used Postgres
-
8.3

k.

Decided on the programming language and t
echnologies used. We have decided to use JSP,
Servlets, Javascript.

R
EQUIREMENT
M
ANAGEMENT
S
YSTEM



Project Report




Requirement Management System, iTeam24x7 © 2008


7

l.

Decided on use of IDE for development. We are using Eclipse IDE.


Phase II: Design Specification Phase (DSD)

a.

Clarification on requirements with Client (Professor)

b.

Defined the components of

the system.

c.

Explained the system structure.

d.

Developed the architectural structure of the system

e.

Define the design class hierarchy of each component.

f.

State the processing narrative for each of the component and their respective operations.

g.

Developed the se
quence diagram for each module.

h.

Defined the internal, global and temporary data structures to be used.

i.

Stated the database description in detail.

j.

Stated the restriction and limitations for each component.

k.

Defined the performance issues for each component

l.

D
efined the design constraints for each component.

m.

Developed the Algorithmic model for each operation.

n.

Stated and explained the dynamic behavior of the system and each of the component.

o.

Worked on the User interface design and stated it in DSD.

p.

Stated the li
mitations, constraints and restrictions for the system in DSD.

q.

Stated the Testing issues.

r.

Defined the testing classes and testing strategy to be carried out to test the system.


Phase III: Testing Phase (TSD)

a.

Followed the testing strategy to test the softw
are.

b.

We have used Unit Testing for source code validation at class level

c.

We have used automated test suite developed in Junit to perform Integration testing at module
level

d.

We have done Functional testing by verifying the requirements. This testing is done

manually. We
have used Black Box strategy for performing functional testing

e.

We have used System testing to validate system as a whole. We have performed security
-
testing,
stress testing under this.

f.

We have asked our friends to act as clients to perform ac
ceptance testing on our software.


Phase IV: Implementation Phase (Source Code)

All coding and unit testing is performed in this phase.


Phase V: Deployment (Project Demonstration, Source Code submission, User Manual and Project
Final Report)


a.

Project is d
emonstrated to Professor on December, 10
th

2008 online using GoTo meeting.

b.

User manual is prepared and submitted on black board.

c.

Project Final Report is prepared and submitted on black board.

d.

Source code is submitted via email. It is also submitted at blac
k board along with user manual.

e.

Received appreciation on our project that Professor will use our project as his demo project in
future classes!!!


R
EQUIREMENT
M
ANAGEMENT
S
YSTEM



Project Report




Requirement Management System, iTeam24x7 © 2008


8

5.0

Future Improvements

TODO: Cleanup of the code and Future Requirements Table

6.0

Source Code

TODO: Give a brief
over view of source code structure and that it is submitted on digital drop box

7.0

User Manual

TODO: submitted on digital drop box.