300144 Object Oriented Analysis
300888 Object Oriented Analysis (Advanced)
Tutorial 3 – CRA & Package (Week 4)
Student Name: ______________________________________
Student ID: ______________________________________
Tutorial Class: ______________________________________
Instructions to students –
• Attempt all questions
• This Tutorial will contribute to your final assessment mark
• The Tutor will check your solutions when you are finished
• BICT (Advanced) students need to complete optional questions.
Project Work:
• Identify major areas of your system based on the case study problem statement (Great Western Real Estate). You need discuss with your group members to identify those major areas likely included in the Great Western Real Estate Management System (GWREMS). It is important at this stage for you to have good understanding to the requirements of the project. If you have not had a detailed reading of the problem statement, it is highly recommended that you reread Section 3 Case Study for Project Work of the template to ensure you and your team members know and understand it fully.
• Undertake Critical Requirement Analysis (CRA) of your business objective and arrive at the Critical Performance Areas of your system.
• Assign the Critical Performance Areas to packages. Thus, the package diagram will now represent the subsystems, or major areas of your project.
• Create and draw a high-level package diagram based on your above work
(Exercise 3). It is essential that each group member of a team should have at least ONE package to work. Therefore, for a project group with four students, it is expected that the team will have at least four packages. These packages will represent the major subject areas of your case study. It is suggested that each group have one or more common packages (such as Emerging Technology Package, or a package in the suggested list but not assigned to any members yet) with the work being shared by all the group members.
• Assign priorities to the packages by using simple percentage figures, in terms of the priority of each package.
• Work out a strategy in your group as to how the group will work together on the PROJECT REPORT, a SINGLE WORD FILE as the final deliverable of the project. This is best done by saving all your weekly work properly and integrating all members’ work in the final report. Please be advised that the integration should be done frequently with the progress of your project work, rather than only at the final stage of the project.
• Observe that the deliverables arising from the Critical Requirement Analysis (CRA) will get updated as a result of the Business Evaluation (BE) undertaken here. Furthermore, the package diagrams may also get updated, as the Business Evaluation may change the scope and understanding of the system. This also indicates the iterative nature of the development in that the CRA and BE processcomponent are feeding into each other. The results of the BE activities update the project report as well as the modelling files using the case tool.
• For each project team, what can be decided at this stage — apart from packages and associated members in charge, are the roles and responsibilities in the project.
In the Business Evaluation Process Component, the primary roles will be that of a Business Analyst with assistance from Domain Experts, Users and End Users.
Besides, every team also needs standard Project Management and Quality Assurance roles for the project. Thus, each team member may need to play different roles.
• Create an iterative and incremental mini project plan for the project work of this week. You can base it on the part of project plan samples showed in Figures 3.9 and Figure 3.11 of Bhuvan’s book. Note that it is important to REPEAT some of the activities and tasks that you undertake as repetition is a very simple yet effective way to facilitate customer evaluation and feedback and adapt to requirement changes. You can take this mini weekly project plan for reference when planning the whole project for the semester.
• Once the plans are complete, undertake and/or cross-check in detail the activities and tasks of the Business Evaluation (BE) process-component and the Requirements Modelling process-component. The work carried out here result in Word and Excel documents that could be included in your project report.
• Each group members are encouraged to investigate different ways of creating packages and prioritising them to form subsystems of the project.
Tutorial Exercises:
• What are the responsibilities of a business analyst within the problem space and what contributions other involved roles can make in the analysis work.
• What are the six best practices of Rational Unified Process?
• Develop Iteratively
• Manage Requirements
• Use Component
• Architectures
• Model Visually(UML)
• Continuously Verify Quality
• (Optional) Modify following Java program based on that given in Lecture 2 to include one more subclass Trapezium. This subclass should include three instant variables topside, base, and height, and you need override method int area (). You can consider using constructors to create objects with the passed arguments, instead of using void set_values (int, int) for setting the instance variables.
class Polygon { int base, height; void set_values (int a, int b) { base=a; height=b; } int area () {
return 0; } }
class Rectangle extends Polygon { int area () {
return base * height; } }
class Triangle extends Polygon { int area () {
return (base * height / 2); }
}
class Polymorph { public static void main(String[] args) { Polygon poly1, poly2, poly3; poly1 = new Rectangle(); poly2 = new Triangle(); poly3 = new Polygon(); poly1.set_values (4,5); poly2.set_values (4,5); poly3.set_values (4,5); System.out.print( poly1.area()
+“\n” + poly2.area()+ “\n“
+ poly3.area()+ “\n”); }
}