List view
- Overdue by 11 year(s)•Due by December 25, 2013•0/2 issues closed
Some description...
Overdue by 11 year(s)•Due by December 2, 2013•16/16 issues closedDeliverables Addressing Feedback: Address any TA feedback on the previous project part. Code Base of Prototype: Your system will be demonstrated in the lab and its source code will be inspected. The code should conform to some consistent coding convention. At this point, your prototype should be implemented to provide something tangible to the user, supporting about half the requirements. Deliver the source code to your source repository. Code Documentation: For each source code file, you should have a brief introductory comment describing its purpose or role within the application or a design pattern, as well as any currently outstanding issues. Provide Javadoc interface documentation for your model and basic command classes and their public methods (at least). Deliver the compiled Javadoc documentation to your source repository. Test Cases: Provide JUnit test cases for your model classes and public methods. The interface to your model should be complete (and documented, above); however, the implementation need not be complete. Applying test-driven development, the test suite should test the entire interface of the model (not only the working part). Some tests will obviously fail because of incomplete functionality, and that is fine. Deliver the test code to your source repository. If you have test data files, also include those. Object-Oriented Design: Document your object-oriented design using a UML class diagram (or diagrams), including more detail on key attributes and methods. Include notes on the use of design patterns among the classes. The diagram(s) may be reverse engineered from the code, but must be edited, arranged, and selective (not a raw dump). The diagram(s) must be developed using eUML2, and embedded as image(s) in your team wiki. The diagram(s) will likely evolve. Release Planning: Plan the major use cases and user stories that need to be done in the final two week period between the end of project part 3 and the end of project part 4 . (This plan can be done near the end of project part 3.) This plan will likely evolve and should be maintained up-to-date in your team wiki. It should be clear from the plan the progress towards satisfying all the specified requirements. Reuse Statement: Document instances of software reuse. Give proper credit to the original developers. Obtain approval for the use of third-party libraries as appropriate. Enter this information in your team wiki. The evaluation of this project part will also include a component called "relative quality". This is used to differentiate projects that meet the minimum from projects that go "the extra mile".
Overdue by 11 year(s)•Due by November 8, 2013•8/8 issues closed###Project Part 2 — Requirements Analysis, Prototyping, Project Plan Learning Objectives #Specify requirements using use cases. #Prototype a user interface. #Conduct an object-oriented analysis. #Form an initial release plan.
Overdue by 11 year(s)•Due by October 25, 2013•5/5 issues closed