Docstoc

OOM Assignment

Document Sample
OOM Assignment Powered By Docstoc
					2008.1 Autumn: OO Modelling Project Report                                        Green ICT Project




    Assignment Cover Sheet                                                                        UTS
    Faculty of IT __________________




    Student Name                   <<All Student Names for the Group to appear here as this is a joint declaration>>


    Student Number                 <<All Student Numbers to appear here in the same sequence as above >>


    Subject Name and               Object Oriented Modelling -


    Number

    Lecturer/Tutor

    Title of Assignment            Project Assignment for Object Oriented Modeling


    Length                         <<Around 70 – replace by your actual number>>


    Due Date                       7 p.m. May 30


    Date Submitted

    DECLARATION
    I hold a copy of this assignment that I can produce if the original is lost or damaged.
    I hereby certify that no part of this assignment/product has been copied from any other student’s work or
    from any other source except where due acknowledgement is made in the assignment. No part of this
    assignment/product has been written/produced for me by another person except where such
    collaboration has been authorised by the subject lecturer/tutor concerned.


    SignatureS: …………………………………………………………………………………………………………..
    ………………………………………………………………………………………………………………………….
    ……………………………………………………………………………………………………………………….

    << ALL STUDENTS IN THE GROUP TO SIGN ABOVE>>




4/3/11                               <<YOUR NAMEs>>                                       Page: 1 of 20
                             6b9d24c4-411e-4a50-8fb9-b9a35422edfc.doc
2008.1 Autumn: OO Modelling Project Report                        Green ICT Project



    <<IMPORTANT NOTES TO STUDENTS OF OO MODELLING
       (READ AND THEN DELETE BEFORE SUBMISSION).


   USE THIS DOCUMENT AS A STARTING POINT (TEMPLATE) FOR THE
    FORMAT YOUR REPORT
   YOU ARE WELCOME TO MODIFY/IMPROVE THIS DOCUMENT
    TEMPLATE.
   SPELL-CHECK YOUR REPORT THOROUGHLY
   THIS IS A PRACTICAL PROJECT REPORT. ENSURE YOUR REPORT
    DOES NOT CONTAIN ANY THEORY (SUCH AS “WHAT ARE
    OBJECTS”) ANYWHERE.
   THE PROBLEM STATEMENT FOR YOUR CASE STUDY IS INCLUDED
    IN THIS DOCUMENT. THIS IS A HYPOTHETICAL PROBLEM
    STATEMENT FOR YOUR CASE STUDY; HOWEVER, IT IS BASED ON
    SOME REAL SYSTEMS DEVELOPED IN THE PAST
   THIS PROBLEM STATEMENT IS PURPOSEFULLY KEPT INCOMPLETE
    AND MAY BE SLIGHTLY CONFUSING (JUST AS MOST REAL-LIFE
    PROBLEM STATEMENTS ARE) - REQUIRING YOU TO CONDUCT
    THOROUGH READING AND DETAILED DISCUSSIONS IN YOUR
    GROUP TO FULLY UNDERSTAND IT)
   IN PRACTICAL PROJECTS, YOU WILL BE CONDUCTING BOTH
    ANALYSIS AND DESIGN. APPROACH THIS AS A PRACTICAL
    PROJECTS. WE ARE NOT DISCUSSING THE PROCESSES HERE, BUT
    YOU CAN FOLLOW THE PROCESS WE ARE FOLLOWING IN THE
    DELIVERY OF LECTURES.
   ONCE YOU START ANALYSIS AND DESIGN, YOU MAY HAVE A NEED
    TO MODIFY THE PROBLEM STATEMENT. ALSO, YOU MAY HAVE A
    NEED TO DEFINE PARTS OF THE SYSTEM THAT ARE “IN-SCOPE”
    AND “OUT-OF-SCOPE”. YOU ARE WELCOME TO DO SO. THUS, THE
    PROBLEM STATEMENT MAY BE MODIFIED BY YOU TO SUIT YOUR
    PARTICULAR UNDERSTANDING OF THE PROJECT
   THE HEADINGS GIVEN IN THIS PROJECT REPORT CORRESPOND TO
    MOST OF THE PROJECT WORK REQUIREMENTS GIVEN AT THE END
    OF EACH CHAPTER OF THE “PRACTICAL OBJECT ORIENTED
    ANALYSIS AND PRACTICAL OBJECT-ORIENTED DESIGN” BOOKS.
    THESE HEADINGS ARE THERE TO ENSURE THAT YOU DO NOT MISS
    ANY MAJOR DELIVERABLES.
   HOWEVER, YOU ARE AGAIN INVITED TO IMPROVE UPON THE
    HEADINGS AS YOU DEVELOP YOUR UNDERSTANDING DURING THE
    SEMESTER. YOU MAY THUS CHANGE THE SEQUENCE AND
    ADD/MODIFY THE HEADINGS IN THIS REPORT




4/3/11                        <<YOUR NAMEs>>                            Page: 2 of 20
                       6b9d24c4-411e-4a50-8fb9-b9a35422edfc.doc
2008.1 Autumn: OO Modelling Project Report                               Green ICT Project


   ENSURE YOU COMPLETE THE COVER PAGE CORRECTLY WITH
    YOUR NAMES AND NUMBERS; ALSO CHANGE THE
    HEADER/FOOTER WITH YOUR GROUP NAMES AND DETAILS
   ENSURE YOU PRINT AND SIGN THE “ASSIGNMENT COVER SHEET”
    PROVIDED AT THE START OF THIS DOCUMENT
   PLAGIARISM RULES WILL BE STRICTLY APPLIED TO THIS VITAL
    ASSIGNMENT!!!
    Please note the following:
    1. Refer to the subject outline for full details on the assignments – marking approach,
    deadlines, academic misconduct etc.
    2. When citing other people’s work in your report, use the Harvard style i.e.
    (Unhelkar, 2007) and don’t forget to include a full reference list
    3. Assignment work is in pairs. The mark awarded for the joint assignment report will
    be allocated to both students equally.
    4. If you have problems during semester with regard to the assignment, contact your
    tutor at the earliest opportunity.
   DELETE THIS INSTRUCTION PAGE AND ALL OTHER INSTRUCTIONS
    EMBEDDED IN THIS REPORT BETWEEN << AND >> NOTATIONS
    AFTER YOU HAVE READ THEM>>




4/3/11                             <<YOUR NAMEs>>                               Page: 3 of 20
                            6b9d24c4-411e-4a50-8fb9-b9a35422edfc.doc
2008.1 Autumn: OO Modelling Project Report                            Green ICT Project




         Object Oriented Modeling - Project Report
                          Green ICT (GICT) Project
                                     Autumn, 2008


                       Green ICT
                  OO MODEL REPORT By


Student                     Last                                  First
  No.                       Name                                  Name




4/3/11                        <<YOUR NAMEs>>                                Page: 4 of 20
                       6b9d24c4-411e-4a50-8fb9-b9a35422edfc.doc
2008.1 Autumn: OO Modelling Project Report                                                                Green ICT Project



                                                 Table of Contents

     History of Document Revision ................................................................................... 5
  1        Executive Summary ............................................................................................ 7
  2        Introduction ......................................................................................................... 7
  2.1      Purpose of the document ..................................................................................... 7
  2.2      Dictionary of Terms and Acronyms ................................................................... 7
  3        Case Study for Project Work & Deliverables ..................................................... 8
     3.1.1      Green ICT (GICT) ...................................................................................... 8
     3.1.2      Background information on the Project ...................................................... 8
     3.1.3      Players ......................................................................................................... 9
     3.1.4      Organizational Portal (OP) ......................................................................... 9
     3.1.5      Regulatory Standards Portal (RSP) ........................................................... 10
     3.1.6      Interactions ................................................................................................ 10
  4        Major Business Function Areas ........................................................................ 11
  5        Scope ................................................................................................................. 11
  6        Package Diagrams ............................................................................................. 11
  7        Class Descriptions ............................................................................................. 11
  8        Class Diagram 1 ................................................................................................ 11
  9        Sequence Diagram 1 ......................................................................................... 12
  10       Use cases for Package 1 .................................................................................... 12
  10.1 Use Case “ “ ..................................................................................................... 12
  11       Use Case Diagrams ........................................................................................... 13
  12       Activity Diagrams ............................................................................................. 13
  13       State Machine Diagram 1.................................................................................. 13
  14       Class Diagram 2 ................................................................................................ 14
  15       Sequence Diagram 2 ......................................................................................... 14
  16       State Chart Diagram 2 ....................................................................................... 14
  17       Component Diagram ......................................................................................... 15
  18       Deployment Diagram ........................................................................................ 16
  19       Project Minutes Of Meetings ............................................................................ 18
     19.1.1     Minutes of the Project Team Meeting of 1/1/2008 ................................... 18
  20       Appendix-A....................................................................................................... 20
  21       Appendix-B: References ................................................................................... 20



History of Document Revision

Version         Released On            Description of Major Revision                              Person
                                                                                                  Responsible


1.0


4/3/11                                           <<YOUR NAMEs>>                                                     Page: 5 of 20
                                       6b9d24c4-411e-4a50-8fb9-b9a35422edfc.doc
2008.1 Autumn: OO Modelling Project Report                        Green ICT Project




4/3/11                        <<YOUR NAMEs>>                            Page: 6 of 20
                       6b9d24c4-411e-4a50-8fb9-b9a35422edfc.doc
2008.1 Autumn: OO Modelling Project Report                        Green ICT Project



1 Executive Summary


2 Introduction


2.1 Purpose of the document




2.2 Dictionary of Terms and Acronyms




4/3/11                        <<YOUR NAMEs>>                            Page: 7 of 20
                       6b9d24c4-411e-4a50-8fb9-b9a35422edfc.doc
2008.1 Autumn: OO Modeling Project Report                                  Green ICT Project




3 Case Study for Project Work & Deliverables
STATEMENT TO BE MODIFIED BY STUDENT GROUPS…


3.1.1 Green ICT (GICT)

<<Note: Following are the requirements for a system called GREEN ICT (GICT). GICT
is a system developed to provide systems support for businesses implementing
Environmentally Responsible Business Strategies (ERBS). This is an example of how in
practical real-life projects, information is initially provided as a set of descriptive pages:
usually half-baked, hardly complete and at times confusing. The requirements below are
more organized than that, but still the students are encouraged to delve deeper into
these requirements to identify what the user wants out of the system. The students will
be able to appreciate how they can further correctly, completely and consistently model
and document these requirements and their designs using the UML. These requirements
also describe the business situation that is so important in understanding the context in
which the project exists. Understanding the context of the project is a crucial ingredient
of the quality process.>>



3.1.2 Background information on the Project

GICT is a software system to be designed to support businesses implementing
Environmentally Responsible Business Strategies              (ERBS). Therefore, GICT is not
software that is specific to a particular industry. In fact, GICT must be able to be used by
various types of industry categories, including both product and service industries.
GICT is to be developed by a group of consultants, who have decades of experience in
the software industry, creating and deploying software solutions for various types of
business problems. YOU are that group of consultants, in charge of developing this
solution. You discover that currently there are no environmentally specific software
packages (such as the existing ERP packages, including those that provide customer
relationship – CRM – and supply chain management – SCM). The consultants have
strategic need of their own to develop a green system from scratch, which will include
the best of breed technologies, including object-oriented designs, an object-relational
database, support for mobile devices and interfaces and implementation in an OO
language (say, Java). The following are the major areas in this project:


4/3/11                              <<YOUR NAMEs>>                                Page: 8 of 20
                             6b9d24c4-411e-4a50-8fb9-b9a35422edfc.doc
2008.1 Autumn: OO Modeling Project Report                                      Green ICT Project


3.1.3 Players

There are number of players (also called stakeholders) in the GICT system. These
players are typically the people responsible within an organization for its ERBS. Thus, in
an airline or a hotel industry, for example, there will be an “Environmental Manager”
who will be responsible for the implementation of the strategies for reducing
greenhouse gases. There will be numerous additional roles in this system, such as the
Workers    responsible   for   entering    the    environmental        data,   the   government
representatives responsible for entering the standards or acceptable benchmarks, and
also the senior management of the organization, who will be interested in having a
bird‟s eye view of the „green‟ performance of their organization.
Furthermore, it is expected that the „general public‟ will also be interested in finding out
the performance of the organization in relation to its green-ness.
In addition to the abovementioned end-users, there are also administrators of the
system, both within the organization and external to the organization, who will be
maintaining the data, information and the applications.
Finally, these users can be individual users and there can be organizational users (who
have individual nominees) who can use this system.



3.1.4 Organizational Portal (OP)

The GICT is made up of two major parts – the Organizational Portal (OP) and the
regulatory standards portal (described next). The OP is made up of organizational data
on its „green‟ performance. These data are updated by the organizational representatives
on an ongoing basis. These data record the organization‟s pollutant performance such as
(a) heat generated by the desktop machines within the organization, (b) carbon
emissions in the petrol/diesel consumed by the organization and (c) non-recyclable and
hazardous materials produced by the organization‟s activities such as lead in batteries
and mobile phones. The organizational portal should be fully customizable to the
industry chosen, and, therefore, it should have the ability to record various categories of
pollutant data. The organizational portal should have the ability to record the energy
ratings of all the devices used within the organization (such as air-conditioners and
fridges). However, the GICT is not meant to store the details of the organization‟s
inventory, but only its carbon emissions. Therefore, there is a need for the GICT‟s
organizational portal to have an interface with the Inventory management system (and
even the supply chain system).


4/3/11                             <<YOUR NAMEs>>                                     Page: 9 of 20
                            6b9d24c4-411e-4a50-8fb9-b9a35422edfc.doc
2008.1 Autumn: OO Modeling Project Report                                   Green ICT Project




3.1.5 Regulatory Standards Portal (RSP)

Regulatory Standards Portal (RSP) is a large portal, maintained by the government of
the country (take, for example, Australia), with detailed and continuously updated
information on the pollutant categories that are producting the carbon emissions. There
are a large number of pollutant categories, which are also growing as new pollutants of
the environment get recognised and added to the list. RSP is made up of thousands of
units of data, examples of which are as follows:
   (a) Various types of pollutants, such as petrol fumes, printer ink and lead
   (b) The approved standard for each of the pollutants – for example, 0.03mg carbon
         per litre of petrol, and 0.05mg of carbon per cartridge of printer ink.
   (c) The variations to the pollutants depending on the type of industry. Currently,
         RSP supports hundreds of industries such as airline, hotel, car rental, packaging,
         computer manufacturers, restaurants, farms etc.
   (d) The standards also vary, depending on the size and location of the organization.
         For example, organizations with less than 20 employees are categorised as small,
         20 to 100 as medium and more than 100 employees as large organizations. The
         same pollutants are allowed in different levels for different size of organizations.
         For example, if a small restaurant is permitted 0.03 mg of carbon per litre of
         petrol use in its commuting activities, a large airline is only allowed 0.025mg of
         carbon per litre of petrol in its activities.



3.1.6 Interactions

Users at both a personal and organizational level need to interact with GICT in various
ways. Thus, some users will be keen to log-in on the organizational website in order to
access GICT, whereas others will be coming in through a handheld device. There is a
need for the system to handle interactions from users who are “in the field” and not in
front of a desktop. Furthermore, each interaction, which can include a query, an update,
a retrieval of data, a check for control total on the green performance and so on, needs to
be stored securely. The privacy of the individuals making those enquiries and updates
need to be secured – especially as this system has the potential to be politically sensitive.


4/3/11                                <<YOUR NAMEs>>                               Page: 10 of 20
                               6b9d24c4-411e-4a50-8fb9-b9a35422edfc.doc
2008.1 Autumn: OO Modeling Project Report                         Green ICT Project




4 Major Business Function Areas
<< HALF TO ONE PAGE LIST OF MAJOR AREAS OF THE SYSTEM. NOTE THAT
IN REAL-LIFE SITUATION, DETAILED ANALYSIS WILL BE UNDERTAKEN IN
ORDER TO ARRIVE AT THIS LIST. HERE, IN OOM, WE IDENTIFY THE AREAS
TO DECIDE WHICH OF THEM ARE IN-SCOPE FOR THIS EXERCISE>>


5 Scope
<<DECIDE THE BUSINESS FUNCTION AREAS THAT ARE IN-SCOPE>>


6 Package Diagrams
<<USUALLY, THESE DIAGRAMS WILL BE DRAWN DURING ANALYSIS. NO
DETAILED DIAGRAM IS REQUIRED – ONLY A LIST OF 4 TO 5 BUSINESS
PACKAGES THAT ARE IN-SCOPE AND THAT WILL BE USED BY YOU, THE
STUDENTS, TO CREATE YOUR MODELS. >>



7 Class Descriptions
<<THIS WILL BE A FAIRLY DETAILED SECTION - PER PACKAGE -
CONTAINING DESCRIPTION OF ALL CLASSES IN THAT PACKAGE; AS A
REMINDER, CLASSES IN OOM WILL CONTAIN FULL DETAILS OF THEIR
DEFINITIONS. THIS CLASS DEFINITION INCLUDES NAME, STEREOTYPES
(optional), ATTRIBUTES (WITH VISIBILITY, ATTRIBUTE TYPES, AND INITIAL
VALUES) AND OPERATIONS (WITH FULL SIGNATURES).



8 Class Diagram 1
<<DRAW DETAILED CLASS DIAGRAMS - PER PACKAGE – BASED ON
INSTRUCTIONS AT THE END OF THE CHAPTER IN PRACTICAL OBJECT-
ORIENTED DESIGN; >>




4/3/11                        <<YOUR NAMEs>>                           Page: 11 of 20
                       6b9d24c4-411e-4a50-8fb9-b9a35422edfc.doc
2008.1 Autumn: OO Modeling Project Report                         Green ICT Project


9 Sequence Diagram 1
<<DRAW DETAILED SEQUENCE DIAGRAMS BASED ON INSTRUCTIONS AT
THE END OF THE CHAPTER IN PRACTICAL OBJECT-ORIENTED DESIGN;
ITERATE AND UPDATE THE CLASSES AND CLASS DIAGRAMS BASED ON
THE SEQUENCE DIAGRAMS>>


10 Use cases for Package 1
THIS IS AN EXAMPLE ONLY OF A USE CASE IN A BANKING CREDITCARD
SYSTEM. YOU NEED TO CREATE SIMILAR USE CASES FOR YOUR SYSTEM,
BUT WITH GREATER DETAILS DURING OO ANALYSIS WORK.


10.1 Use Case “ “


         Use Case:
         Actors:
         Description:
         Pre-Condition:
         Post-
         Condition:
         Type:
         Normal Course      1.
         of Events:
         Alternate
         Course of
         Events:
         References




         Use Case:
         Actors:
         Description:
         Pre-Condition:
         Post-
         Condition:
         Type:
         Normal Course
4/3/11                        <<YOUR NAMEs>>                           Page: 12 of 20
                       6b9d24c4-411e-4a50-8fb9-b9a35422edfc.doc
2008.1 Autumn: OO Modeling Project Report                         Green ICT Project


         of Events:




         Alternate
         Course of
         Events:
         References         Name of Author; Additional references to other
                            documents.



11 Use Case Diagrams



12 Activity Diagrams


13 State Machine Diagram 1
<<DRAW DETAILED STATE MACHINE DIAGRAM BASED ON INSTRUCTIONS
AT THE END OF THE CHAPTER IN PRACTICAL OBJECT-ORIENTED DESIGN;
ITERATE AND UPDATE CLASS AND SEQUENCE DIAGRAMS, BASED ON
SMD>>




4/3/11                        <<YOUR NAMEs>>                           Page: 13 of 20
                       6b9d24c4-411e-4a50-8fb9-b9a35422edfc.doc
2008.1 Autumn: OO Modeling Project Report                               Green ICT Project



<<following headers are similar to previous class, sequence and state, use case and
activity diagrams, but now repeated for another package – typically by another
student>>


14 Class Diagram 2

15 Sequence Diagram 2


16 State Chart Diagram 2


… AND SO ON.




4/3/11                            <<YOUR NAMEs>>                              Page: 14 of 20
                           6b9d24c4-411e-4a50-8fb9-b9a35422edfc.doc
2008.1 Autumn: OO Modeling Project Report                         Green ICT Project




17 Component Diagram
<<ONE FOR THE SYSTEM – AS PER INSTRUCTIONS IN PRACTICAL OBJECT-
ORIENTED DESIGN>>




4/3/11                        <<YOUR NAMEs>>                           Page: 15 of 20
                       6b9d24c4-411e-4a50-8fb9-b9a35422edfc.doc
2008.1 Autumn: OO Modeling Project Report                         Green ICT Project




18 Deployment Diagram
<<AS PER INSTRUCTIONS IN PRACTICAL OBJECT-ORIENTED DESIGN>>




4/3/11                        <<YOUR NAMEs>>                           Page: 16 of 20
                       6b9d24c4-411e-4a50-8fb9-b9a35422edfc.doc
2008.1 Autumn: OO Modeling Project Report                         Green ICT Project




4/3/11                        <<YOUR NAMEs>>                           Page: 17 of 20
                       6b9d24c4-411e-4a50-8fb9-b9a35422edfc.doc
2008.1 Autumn: OO Modeling Project Report                           Green ICT Project


<<THE ADMINISTRATIVE PART OF THIS PROJECT>>


19 Project Minutes Of Meetings
19.1.1      Minutes of the Project Team Meeting of 1/1/2008

Meeting No: 1                       Held at: Parramatta Lab / Campus library / etc.
Chairperson:                        Jamie Yang
Team members in attendance:         <<Full names>>

Minutes taken by:                   Jamie Yang

Agenda items discussed:

   1. Interpretation of the case study GICT……….

   2. Identifying initial classes ………………….




4/3/11                        <<YOUR NAMEs>>                              Page: 18 of 20
                       6b9d24c4-411e-4a50-8fb9-b9a35422edfc.doc
2008.1 Autumn: OO Modeling Project Report                             Green ICT Project


Action Plan:

               Description                    Who              When       Initial
Item



Agenda for Next Meeting:
  Next meeting will be held at 2/8/2008, Monday, at xyz Coffee shop. Tentative
  agenda items include:

   1.
   2.
   3.
   4.


Acceptance of minutes:
Jamie _______________________
Amit _______________________
Sam _______________________
Mary _____________________
Nick_____________________




4/3/11                         <<YOUR NAMEs>>                              Page: 19 of 20
                        6b9d24c4-411e-4a50-8fb9-b9a35422edfc.doc
2008.1 Autumn: OO Modeling Project Report                         Green ICT Project




20 Appendix-A

21 Appendix-B: References
Etc.




4/3/11                        <<YOUR NAMEs>>                           Page: 20 of 20
                       6b9d24c4-411e-4a50-8fb9-b9a35422edfc.doc

				
DOCUMENT INFO