Object Oriented Analysis and Design Assignment 1 Semester 2 2016 - Case study Student must complete the following: a. Analysis documentation should include: Analysis – Requirements list including functional and non-functional, Actors and Use Cases, Prototypes, Initial Architecture, Communication diagrams, Class diagram with generalization / aggregation structures, Activity diagrams, and Sequence diagrams Due 25 October 2016 weighting 35% b. Design and implementation documentation should include: Design – Design Issues, Architecture (layering, component interaction, and concurrency issues), Refine class diagram with associations, State Charts, Interface issues, Pattern issues, Human interaction issues, Database design, Expansion of diagrams where required (activity diagrams, sequence diagrams) Implementation - Component diagram, Deployment diagram, Testing aspects, User Manual and Training Strategy, and Implementation Strategy. Due 15 November 2016 weighting 35% Marks: 100 per section Instructions: Carefully read the case study for this assignment. Students will be turning in the assignment individually (but may cooperate in pairs – however, you must talk to the lecturer for approval). Assignments must be word-processed, look professional, and the diagrams must be produced using Visio or similar tool. Place your assignment in the collection box in the IT building, and submit an electronic copy through the link on EIT online by 8.15am on the due dates. Object Oriented Analysis and Design Case study: Electronic Non-Profit Organization E-NPO The purpose of this assessment is to allow the student to use their analysis and design skills to interpret a given specification for modelling and developing an Information System. The specification is given in a case study which mimics a real world application. The Case Study Object Oriented Analysis and Design Case study: An International Non-Profit Organization (E-NPO) Note: This case study is fictional and bears no relation to an actual project. Background The Electronic Non-Profit Organization (E-NPO) is a new international entity, sponsored by a major intergovernmental organization, assisting in the provision of assistance and teaching to developing areas around the world via mobile technology and m-learning. There is a competent team of staff ready to work in this agile organization. With wireless internet growing around the world, the organization is optimistic about its future impact. The Electronic Non-Profit Organization (E-NPO) has a system development office in Wellington, New Zealand while the company's teaching and operational staff are telecommuting or connecting from around the world. The Electronic Non-Profit organization (E-NPO) conducts its actual social service work outside New Zealand. The Electronic Non-Profit Organization (E-NPO) is created to use up-to-date mobile technology and the internet effectively for fundraising, community building, providing information resources to volunteers and locals, and inter-organizational collaboration. The organization also specializes in mobile learning (m-learning), which involves the use of smartphones and tablets. Furthermore, the courses are geared toward work related training and social service. Therefore, the organization is constantly available online. Company Details Organization: The Electronic Non-Profit Organization (E-NPO) Philosophy: Pervasive Computing Sponsor Name: Samuel Ekundayo Sponsor Title: Director Sponsor Address: United Nations Road PO Box 123456 Auckland New Zealand Contact Phone: +64 9 9799 432 Contact Email: [email protected] The Electronic Non-Profit Organization (E-NPO) wants you to develop a new Information System to handle fundraising, payments to suppliers, accounting, human resource management, content creation, and online teaching. Scope and Purpose of the project There is a significant need to provide immediate information such as emergencies to staff and volunteers around the world. Furthermore, mobile learning and 'mobile-assisted language learning' in particular are seen as solutions for providing basic education and information in different parts of the world. Electronic Non-Profit Organization (E-NPO) needs to provide non-profit services to various stakeholders (individuals, staff, other organisations, etc.). The aim of E-NPO is to provide technical and language education and global information while minimizing costs and administrative inefficiencies. All aspects of operation need to be incorporated into the information system, in addition to being an efficient and mobile solution. E-NPO hopes to handle a great amount of communication and education activity, and needs to be well supported by the day-to-day administrative processes in accomplishing a high degree of stakeholder satisfaction. It is important to maintain detailed regional and cultural information to support community building, education, public information, and international development projects. E-NPO adheres to specific paradigms which you will also need to research and understand while completing the assignment: 1) microlearning, 2) modern object-oriented system development methodologies, and 3) pervasive (ubiquitious) computing. A new Information System needs to be developed in order to manage all activities, optimize collaboration, improve internal processes and achieve excellent service levels, all helping global development and education. Aspects to be included in the Electronic Non-Profit Organization (E-NPO) system are: • Individual and group enrolments • Online content management • Payments from donors / to suppliers • Accounting / Payroll / Finance • Human resource management • Reports to Director and higher organizations • Quality Control and availability at low costs Once designed and implemented, the sponsor will assign staff responsible for uploading content into the system and for maintaining it in the future. This project will support or impact the following business processes and departments: 1. Online Registrations 2. Accounting for Fundraising 3. Social Information Services 4. Technical Support 5. Internal Administration 6. Online Language Teaching 7. Management of Teaching Content The project scope may need to be altered over the course of the project. Should the project scope be changed, all relevant parties should be notified and come to an agreement to minimize delays regarding the progress and completion of the project. The project manager is responsible to conduct any means of communication if the project scope is in need of adjustment. What to Do: Develop the documentation specific to this type of Information System to incorporate: payments (from donors and to suppliers), course enrolments, online content management, emergency information, resource management, and the delivery of technical and developmental assistance to your stakeholders along with quality and user-friendliness. This is an individual assessment but you may talk to each other during the tutorials. Students are expected to analyse, design and develop the implementation documentation that meets the requirements as specified. Requirements Develop the documentation for the above case study. It should include the following: Analysis - • Requirements list: functional as well as non-functional = ALL • Actors and Use Cases = ALL including 2 mock prototypes • Initial Architecture Discussion = Showing ALL subsystems • Communication diagrams = 5 examples – at least two with more than one entity class association. • Class diagram with generalization and aggregation structures – Full System • The class diagram file needs to be shared with the lecturer through Google Drive (share your file with [email protected]) • Activity diagrams = 5 examples • Sequence diagrams = 5 examples (at least 3 with 2+ entity class interaction) Design – • Design Issues and expansion of 2 activity diagrams • Agile approach and documentation (Scrum template and video) • Architecture: layering, component interaction, and concurrency • Refine class diagram (incl. data types) • State charts => at least 5 state charts • Interface (+ human interaction) issues • Pattern issues, incl. at least 2 patterns • Functional Prototype in small groups: a) A quick website (Google Site) or b) A simple mobile app (Appy Pie) Implementation • Component diagram • Deployment diagram • Testing: various aspects • Implementation strategy • User manuals strategy • Training strategy Marking Schedule ITSD7.330 OOAD Task Mark Achieved ANALYSIS: 100 (Total) Formatting, Consistency, and Prototypes 10 Requirements list: functional and non-functional 15 Actors and Use Cases 15 Initial Architecture 15 Class diagram with generalization and aggregation structures 15 Activity diagrams 10 Communication diagrams 10 Sequence diagrams 10 DESIGN and IMPLEMENTATION: 100 (Total) Design issues and expansion of analysis documentation, and formatting 15 Architecture: layering, component interaction, concurrency issues 10 Refine class diagram (data types, constraints) 10 State charts 10 Small functional prototype 10 Interface and Pattern issues 10 Agile/Scrum documentation 10 Reflective video or Powtoon 5 Component diagram 5 Deployment diagram 5 Testing aspects and Implementation strategy 5 User manuals strategy and Training strategy 5