CS 389 Software Engineering MultiLib 2008 Final Presentation Adam Pitzer -Team Leader Paul Dumoulin - Quality Manager Miguel Vega - Wiki Master Steve Malko - Web Designer Juan C. Arias - Client Liaison/Documentation Manager Junming Mei - Development Coach Software:

MultiLib *Operating Context *Software Engineering Process *Software Requirements *Software Architecture *Design *Database Design *Coding *Testing *NYC Developer Task List

What is the MultiLib 2008 Project? *It is a global software development project in which multiple universities will compete to create an online library system for the computer science department of the Institute of Technology of Cambodia (ITC). *Students from Pace, Bank of New York, ITC, The University of Delhi and Mahidol University in Bangkok will take part in this project.

Cambodian Client Team

Role of Cambodian Client Team *5 students, each a sponsor and contact for one of the 5 development teams. *Own and manage the project requirements. *Supported by a team of US Graduate client quality Coaches. *Manage interactions and communication with the development teams. *Prepare a testing strategy for developed systems.

USA1-NYC Development Team

Role of USA1-NYC Development Team *Review and clarify software requirements. *Suggest candidate designs. *Show how designs satisfy requirements. *Solicit feedback from client contact on design. *Review and answer Dev. Coach comments. *Answer Auditor’s questions and comments. *Implement design. *Post all project documents on Wiki. *Prepare a testing strategy. *Deliver tested software to client.

USA1-NYC Development Coach * Responsible for quality of the software development process and assuring quality of software product. * Assisted with software process and project planning. *Assured developer Wiki was up to date for auditing purposes. *Coordinated external process audit with team Auditor’s. *Maintains weekly communication survey and Wiki log detailing what was done to improve and why.

NYC Auditors

Role of NYC Auditors *Review design document and provide feedback. *Conduct audit of the development team’s Wiki and of all posted documentation. *Communicate with the development coach on health of project and Wiki.

Auditor’s Task Chart

Client Coaches

Role of Client Coaches *Supervised change management and the requirement Wiki for Cambodian client. *Clarified requirements issues. *Facilitated communication with client team.

Communication Overview

Overall Communication Method of Communication# s sent to Client?32 Scheduled chats with client?12 Unscheduled chats with client?3 s to client coaches?4 Chats with client coaches?6 s to development coaches?9 Chats with development coaches?1 s to Auditors?7 Chat with auditor?0 Face to Face meetings of developers?20 Face to Face with development coaches?0

Setbacks and envisioned risks *Language barriers miscommunications *Client limited access to Internet *Time zones, there is a 12 hour difference *Skill level of development team members *Requirements may lack information *High level changes may be necessary late into the project *Unforeseen bugs may exist. *Poor documentation and sloppy code may slow tests and fixes *Time frame of project (end of school term)

Software Engineering Process *Requirement Phase – Waterfall process was used. *Coding Phase- Agile methodology, pair programming. *Multiple functional iterations.

Software Requirements *Requirements were provided by client coach. *Finalized through client chats and s. *Waterfall process used to minimize changes. *Design document prepared to show client how requirements were to be implemented.

Functional Requirements

Non-Functional Requirements *User friendly interface *Unicode compatible interface *Performance *Security *Backups *Language & Support *Maintainability & Extensibility

Software Architecture

Database Design

Coding *Programming language – Java *Vulcan was used as a testing and development environment. (vulcan.seidenberg.pace.edu) *An iteration table was created to show which requirements were implemented. *Implemented requirements were released in 3 iterations.

Testing * Testing Plan. *Verify software to satisfy original design. *Validate – does product fit intended use? * Use of dynamic testing methodologies (test cases, unit testing, integration testing and system testing).

MultiLib Graphical User Interface

Case Tools Software Engineering Phase TaskTools Used DesignUSE Case DiagramArgo UML DesignClass DiagramArgo UML DesignERDDB Designer 4 DesignGUIDreamweaver DesignHigh Level Architecture DesignArgo UML DesignDatabaseMySQL DesignRunning ScriptsTomcat TestingUnit TestingJUnit TestingBug Tracker / Source Code RepositoryJava.net CodingIDE (Integrated Development Environment)Eclipse

NYC Developer Task Chart TasksAdamPaulMiguelSteveJuanTime Review of Requirement Document XXXXX6 hours Wiki UpdateX5.5 hours Design DocumentXXXXX10 hours Database DesignXX8 hours Midterm Presentation X3.5 hours Client ContactXX4.5 hours CodingXXXXX14 hours Final PresentationX6 hours TestingXXXXX7 hours User ManualX2 hours

Project Status as per Auditors * Project Health is at a status of “YELLOW”.

Conclusion *Although we were able to implement most of the requirements, the MultiLib program was not completed. *Time constraint was the main reason. Communication with the client team was challenging. *Working in groups was both a challenging and rewarding experience. Interacting and completing with foreign students gave us a taste of real world business practices.