Overview

Weighting : 25%
Method of submission : Blackboard Assignment 2
Report upload link (report only) Project upload link (this will include all files in a compressed file, eg presentation, VS files, Gantt chart, meetings eg excel) Individual peer review link File Name : groupName_report_ass2 (One Turnitin per group) groupName_project_ass2 (One compressed file per group) groupName_stud#_peer_review File Type : Word/pdf and one compressed folder

Concept

This is Part 2 of your Two-Part assignment.

Peer review:

Your individual contribution to the team and your assignment mark will be peer-reviewed. Each team is to include the Peer Review document (available on the course Blackboard Assessment Menu) as an individual submission. The Peer Review document will indicate the tasks assigned and relative contribution and by each member of the team to the final work. This should be done using a percentage, in a similar manner to being paid $100 for the work and having to divide it between the contributing members. If there is a dispute in allocation, the lecturer will assess individual team member contribution at a meeting and the Gantt chart, this must be up to date. (make sure you keep all your working documentation that also shows your individual effort as this will be used in the evaluation of member’s contribution by the lecturer).

Team Management:

Each team should continue to upload their progressive project schedule and weekly minutes to the group’s file exchange area on Blackboard. These minutes will form an ongoing part of the assessment for the assignment. The team minutes may also be used to assist determination of member contribution and quality in case of a dispute between team members.

Weeks 9-12

You should proceed with the detailed design of an agreed part of the system. For this:
You will develop a design (detailed) class diagram and some state diagrams for each relevant class. You will develop detailed use case descriptions of selected use cases (proposed system). For each of these selected use cases you will develop design (detailed) sequence diagrams. You will develop design screens that will simulate the functionality of your selected use cases.

Note: the class structure (attributes and methods) of your class diagram should be consistent with the sequence and state diagram messages, and the functionality and data used in your screens should be consistent with all of your models.

You will also be required to provide an implementation strategy, training, and testing and maintenance procedures for your developed system. A test plan and test data bank will be created that will adequately test your selected use cases and some example business rules. These will be judged from a practical (rather than theoretical) viewpoint.

The Project Management Discipline indicates that you should start to think of a work breakdown structure, identifying the activities that your group will undertake, the resources required, the time involved in each. There may be some use cases that you cannot estimate and these would be identified as risky ones. The theory indicates that use cases with the most risk would be considered first to determine what is involved in their development. Other sources of risk would be identified and contingency strategies prepared for implementation in case they occur (risk matrices help here but are not required in the assignment). Monitoring points would be planned and added to the developing Gantt Chart.

Presentation:Week 12 during class, ALL members are to be present.

Assignment Research and Readings

Satzinger, J.W., Jackson, R.B., Burd, S.D. (2005) Object-Oriented Analysis and Design with the Unified Process Thomson Publishing Co. Satzinger, J.W., Jackson, R.B., Burd, S.D. (2016) Systems Analysis and Design in a Changing World Cengage Learning.
Note: Earlier editions of this book are useful. Schwalbe, K. (2014) Information Technology Project Management (7th Ed) Cengage Learning.
Note: Earlier editions of Schwalbe are equally good. Further resources as specified in the Blackboard course site.

Assignment Requirements

Your group is to submit one word document which will have the following major sections:

Group Assignment cover sheet Executive Summary o Some ideas for writing executive summaries:
unilearning.uow.edu.au www.businesswritingblog.com Table of contents Introduction System Implementation and Risk Management System Design Conclusion Reference Appendix
Group Management Documents eg weekly meetings, task allocations Individual Peer Review Document (To be uploaded to BB) Visual studio file, Gantt chart and weekly meetings (if an excel sheet), and diagram file/s as one compressed file

Detailed Submission Description

System Implementation and Risk Management - (20%) Implementation Plan: (how the system is to be implemented and integrated into the organisation, covering aspects shown below). How the Business rules will be implemented (at a design level and in code). This is an updated version of your first submission. You must show how this has changed and why as the project has developed. Testing; Training; Data Migration (if required); Installation Plan (hardware and software installation); Maintenance. Risk Management: A list and Ranking of major risks for the project (if there are any). To help with this you might like to consider the following questions: What use cases involve risk? Is there any risk that requires Professional Liability insurance? Are there any ethical considerations that will need to be considered – If so, what are they? Are there any special privacy or security conditions expected by the client? Are there any special commercial considerations, for example, how will Intellectual Property be addressed? This is an updated version of your first submission. It will have new risks such as data migration or implementation issues or team skills in developing system interfaces etc. You must show how this has changed and why as the project has developed. So the risks will include the project and your team. System Design - (65%) The following diagrams will be images placed in your word document. Make sure they are of an appropriate resolution, you may be asked to show the viso (or working files of other software) files as part of the grading. A revised Use Case diagram showing the proposed expansion/improvement, plus detailed use case descriptions for two selected use cases (assigned by the instructor). A Design Class diagram for the accepted proposed system (Use Case functionality). (Controller classes should be included). Only major, important methods should be included in classes – please note that create ( ) and delete ( ) are default methods that are assumed for all classes and need not be shown in the class diagram for your proposed system. Classes and associations need to be labelled, multiplicity (min and max) indicated and important attributes identified. Detailed System Sequence diagrams for two selected use cases (assigned by the instructor). map this back to the two use case detailed descriptions. Must include the classes that are represented in your design class diagram. StateChart Diagrams for two selected classes (assigned by the instructor). Screen Designs for the following use cases: Main navigation menu (to allow navigation to the following forms) Logon Teaching period time line Course outlines Class Timetabling Exam Process Meetings School guidelines (eg process for exam review or forms) Report view timeline eg what tasks and who is completing them or has completed them etc A user must be able to navigate between each prototype interface The Interfaces does not have to connect to any database but they should have some realistic data in list boxes, combo boxes, etc., that will display their functionality. No error checking etc. is required. Presentation and Project Management - (15%) Your team will present the submission in your class in week 12 or via a video for online. This should be done as a formal presentation to the management of your client’s organisation (and to the other teams in the class). The presentation will run for 15 minutes plus time for questions. Your project management documentation will form part of the assessment of how your team managed themselves. This will include any change management, weekly meeting and task allocation. Individual Peer Review - Please note that this is a mandatory component The document is to be uploaded to BB The team allocates a % contribution for each team member, covering the contribution from each team member through the trimester and towards the final assignment submission. (The combined total of all members’ contribution should be approximately 100%). You also need to include the asks eg sections that a team member has been assigned. If there are any issues then you will be asked to show your individual working documents and the Gantt chart.

Additional Information:

Be aware of the University policies for plagiarism and copying another person’s assignment. If you are caught you will be reported to the SACO. Reference (APA) all work where required. If is not your own words or work (this includes images), then references from where you sourced the material are required. References that are a not a book of journal must include the retrieve date (for this course). APA referencing style, a guide is in the course materials menu. Footer: with page number and your group name

To Download Click Here > INFO6030 Assignment 2.pdf