Sale!

System Development Assignment 2

$30.00

CSCI222
System Development

Assignment 2 – Group Assignment (30 marks)

TASKS
Your tasks are to:
•    Reorganize your group, re-allocating roles and responsibilities to your members (your members should be the same as in Assignment 1);
•    Complete the design, implementation and testing of the Warehouse Management (WM) Tool  as specified in the first assignment.
•    Produce a report detailing the group’s work.

Category:

Description

5/5 - (2 votes)

CSCI222
System Development

Assignment 2 – Group Assignment (30 marks)

TASKS
Your tasks are to:
•    Reorganize your group, re-allocating roles and responsibilities to your members (your members should be the same as in Assignment 1);
•    Complete the design, implementation and testing of the Warehouse Management (WM) Tool  as specified in the first assignment.
•    Produce a report detailing the group’s work.

SUBMISSION
The submission must include a hard-copy of the report and a CD containing a copy of the report, an executable version of the system, all UML models, source code, and test cases.  In addition, a product demonstration is required during your last lab session.
The report should be structured as below:
•    A summary of your group’s work on design and implementation.  This should cover design artefacts including architectural design, use cases, sequence diagrams, class diagrams, state diagrams, data persistence and user-interface design.  UML modelling diagrams should be used to illustrate design decisions.
•    A brief presentation that illustrates the actual implemented product.  This presentation should combine text commentary with information captured from actual execution of programs (as screen shots or as captured text inputs and outputs).  This presentation should clarify which of the functional requirements have been successfully implemented.
•    An accurate summary detailing exactly what aspects of the requested functionality are fully implemented in your solution.

•    Details of the construction phase.  This part of the report should clarify the work planned and done in each iteration.
o    Summarize the new elements added and the extensions to existing implementation elements.  Include brief details of unit testing procedures used to verify new elements prior to their commitment to the project (this does not mean list unit test code and test outputs, simply identify the additional tests created by individual implementers).
o    Summarize data from defect and integration reports created by the systems integrator.
•    Code
o    Code listings for all elements in the final product should be included in an appendix to the main report.
o    Samples should be provided of support code such as the unit test classes created to verify particular application classes.
•    Testing:
o    Test plans, test cases and test reports should be provided.

The “meta-report” part should include:
•    A tabular summary of the group structure identifying group members, the roles that they filled, the artefacts that they successfully delivered.
•    Group meeting records and individual diaries:
o    There should be a summary detailing the work done at each group meeting.
o    There should be agendas and reports from all group meetings.
o    There should be work diaries of all members of the group.

SUBMISSION
Your group is to submit a hardcopy of the report to the lecturer as well as upload a softcopy to moodle before deadline. The report must contain a “member contribution assessment” section.  This should identify the member contributions on the ordinal scale “contributed”, “some contribution”, “almost no contribution”, or “no contribution”.  This section must be signed by all group members.

MARKING SCHEME
•    Overall presentation of report  (3 marks)
•    Analysis and Design  (10 marks)
•    Sophistication of the solution (4 marks)
•    Project management  (4 marks)
These marks are based on evidence for the use of an effective software development process. Factors contributing to this part of the assessment will include: evidence for an effective group structure and adoption of roles; effective group collaboration as evidenced by meaningful group meetings; well-planned and disciplined work processes of individuals; and effective use of a versioning system.
•    Code and testing (5 marks)
This part of the assessment will be based on the quality of the implementation code, and evidence for testing such as the unit test code, test cases and test reports. The code should, of course, use properly organized header and implementation files for classes; good coding style is required; elements written by different implementers should be consistent in style (the group should adopt conventions for naming and structuring of code that are used by all implementers).  The code should not contain errors.  Control flow should be well structured.
•    Product demonstration (4 marks)
Individual marks are based on the group mark.  Individual marks are adjusted in accord with the “member’s contribution assessment” document submitted by the group. Individual marks cannot be greater than the group mark.