EEL-5881
Software Engineering Project: Research Expert
Project Legacy |
Research Expert
Project Legacy
EEL 5881, Fall, 2008
Team Name: Team 3
Team Members:
Roles
|
Task |
Team Member |
Role |
% of Contribution |
| Concept of Operations |
Joshua Thompson |
Provided information on current system and needs, user and mode of operations, operational scenarios and features, expected impacts and analysis of proposed system |
100 |
| Software Requirements specification |
Paul Varcholik |
Determined software to be produced, product overview, specific requirements and use case diagrams |
100 |
| Project Management Plan |
Prabhavathi Kumarasamy |
Determined the project time schedule, life cycle model, configuration management, risk management and all aspects relating to project management. |
100 |
| High-Level Design |
Joshua Thompson Prabhavathi Kumarasamy |
Provided diagram of major components of the system and their interfaces and design issues |
50 50 |
| Detailed Design |
Joshua Thompson Prabhavathi Kumarasamy |
Provided information on design issues, detailed design information with database and class diagrams and trace of requirements to design. |
50 50 |
| Test Plan |
Joshua Thompson |
Determined test environment and test cases to be used in the project. |
100 |
| Test Results |
Joshua Thompson |
Test plan procedures were followed and documented pass/failed results. |
100 |
| User's Manual |
Prabhavathi Kumarasamy |
Provided the description of the system, screen shots and example for the users. |
100 |
| Source Code |
Paul Varcholik |
Provided source code developed using ASP .net, C# |
100 |
| Build Instructions |
Joshua Thompson |
Described all code, data, procedures and documentations |
100 |
| Project Legacy |
Prabhavathi Kumarasamy |
Provided the roles and analysis of all product and process metrics. |
100 |
| Final Presentation |
Joshua Thompson Prabhavathi Kumarasamy Paul Varcholik |
Prepared the presentation slides |
Equal effort by all team members. |
Analysis
Quality of final product:
The Research Expert system meets the high priority requirements of the clients. It's fully functional and upto the expectations of the clients. It is well designed and robust with maintainable code.
Code Statistics:
- 180 files
- ~ 4,500 lines of code
- 57 classes and enumerations
- 15 database tables
- 88 database stored procedures
- 87 unit tests
Known Problems:
The test was conducted by following the test plan. The product add, delete, modify, store and return data correctly. The results were as expected.
Adherence to Project Plan:
The project work was smooth and we were on time until second deliverable. But for the final deliverable, we had only limited time to finish the codings and to bring the product fully functional. As the project is big and to finish the project on time, we haven't implemented some of the requirements. Each team members have contributed their effort and had good communication as well.
Defect Analysis:
Some of the show-stopper and low priority bugs were cleared. There are some minor cosmetic user interface errors that will not be addressed. Overall, not much defects are documented.
Quality Assurance:
Quality of the product and satisfying the clients was the top priority of the project. The product was tested from the first phase using NUnit software. The testing was done parallel with each task for its correctness. All team members reviewed the work after completion. Quality wise the product yielded all the results that we had expected. We gave the updates and links to the client for acceptance testing. No comments from him. So, our team concluded that the acceptance testing was completed.
Configuration Management:
We performed adequate activities for configuration management. Perforce software was used for checking the significant modifications. One person is responsible for configuration management. The other team members can get access only to the granted task.
Suggestions for the Future:
-
Keep good communication between team members.
-
Assign tasks to the team members they are knowledgeable and familiar with.
-
Choose a project that you can finish it on given time schedule.
-
Good project estimation and time scheduling are important factors to avoid project failures.
If the project is 10 times bigger, we will keep the life cycle process, documentation and the change will be more group meetings, better time schedule. For the project 100 times bigger, we will keep the lifecycle process and the change will be improved configuration management, better documentation, effective testing methods.
