Faculty of Health, Engineering and Science

School: Computer and Security Science

This unit information may be updated and amended immediately prior to semester. To ensure you have the correct outline, please check it again at the beginning of semester.

  • Unit Title

    Software Design
  • Unit Code

    CSI6109
  • Year

    2015
  • Enrolment Period

    1
  • Version

    1
  • Credit Points

    20
  • Full Year Unit

    N
  • Mode of Delivery

    On Campus
    Online

Description

This unit explores object orientation as a software development method as well as other software design methodologies.Issues such as object oriented persistence techniques, different programming environments and software implementation issues will also be addressed.

Equivalent Rule

Unit was previously coded CSI5101

Learning Outcomes

On completion of this unit students should be able to:

  1. Apply contemporary modelling techniques.
  2. Apply current design and software specification methods and processes.
  3. Apply programming and implementation issues.
  4. Investigate and develop the user software interface.
  5. Reflect on the software design process.

Unit Content

  1. Comparative software design methodologies.
  2. Conceptual modelling for object-oriented development.
  3. Development environments.
  4. Programming and implementation issues.
  5. Software specification.
  6. The object-oriented paradigm.

Additional Learning Experience Information

Lectures, workshops, exercises, research and project.

Assessment

GS1 GRADING SCHEMA 1 Used for standard coursework units

Students please note: The marks and grades received by students on assessments may be subject to further moderation. All marks and grades are to be considered provisional until endorsed by the relevant Board of Examiners.

ON CAMPUS
TypeDescriptionValue
AssignmentTeam based software prototype15%
ProjectCompleted software project25%
Examination ^End of semester examination60%
ONLINE
TypeDescriptionValue
AssignmentTeam based software prototype15%
ProjectCompleted software project25%
Examination ^End of semester examination60%

^ Mandatory to Pass

Text References

  • ^ Schach, S. (2010). Object oriented and classical software engineering (8th ed.). Boston, MA: McGraw Hill.
  • Douglass, B. (2000). Real-time UML (2nd ed.). Reading, MA: Addison Wesley.
  • Booch, G., Maksimchuk, R.A., Engel, M.W., & Young, B.J. (2007). Object-oriented analysis and design with applications (3rd ed.). Reading, MA: Addison Wesley.
  • Arlow, J., & Neustadt, I. (2005). UML 2 and the unified process (2nd ed.). Reading, MA: Addison Wesley.
  • Binder, R. (2000). Testing object-oriented systems - models, patterns, and tools. Reading, MA: Addison-Wesley.

^ Mandatory reference


Disability Standards for Education (Commonwealth 2005)

For the purposes of considering a request for Reasonable Adjustments under the Disability Standards for Education (Commonwealth 2005), inherent requirements for this subject are articulated in the Unit Description, Learning Outcomes and Assessment Requirements of this entry. The University is dedicated to provide support to those with special requirements. Further details on the support for students with disabilities or medical conditions can be found at the Access and Inclusion website.

Academic Misconduct

Edith Cowan University has firm rules governing academic misconduct and there are substantial penalties that can be applied to students who are found in breach of these rules. Academic misconduct includes, but is not limited to:

  • plagiarism;
  • unauthorised collaboration;
  • cheating in examinations;
  • theft of other students' work;

Additionally, any material submitted for assessment purposes must be work that has not been submitted previously, by any person, for any other unit at ECU or elsewhere.

The ECU rules and policies governing all academic activities, including misconduct, can be accessed through the ECU website.

CSI6109|1|1

Faculty of Health, Engineering and Science

School: Computer and Security Science

This unit information may be updated and amended immediately prior to semester. To ensure you have the correct outline, please check it again at the beginning of semester.

  • Unit Title

    Software Design
  • Unit Code

    CSI6109
  • Year

    2015
  • Enrolment Period

    2
  • Version

    1
  • Credit Points

    20
  • Full Year Unit

    N
  • Mode of Delivery

    On Campus
    Online

Description

This unit explores object orientation as a software development method as well as other software design methodologies.Issues such as object oriented persistence techniques, different programming environments and software implementation issues will also be addressed.

Equivalent Rule

Unit was previously coded CSI5101

Learning Outcomes

On completion of this unit students should be able to:

  1. Apply contemporary modelling techniques.
  2. Apply current design and software specification methods and processes.
  3. Apply programming and implementation issues.
  4. Investigate and develop the user software interface.
  5. Reflect on the software design process.

Unit Content

  1. Comparative software design methodologies.
  2. Conceptual modelling for object-oriented development.
  3. Development environments.
  4. Programming and implementation issues.
  5. Software specification.
  6. The object-oriented paradigm.

Additional Learning Experience Information

Lectures, workshops, exercises, research and project.

Assessment

GS1 GRADING SCHEMA 1 Used for standard coursework units

Students please note: The marks and grades received by students on assessments may be subject to further moderation. All marks and grades are to be considered provisional until endorsed by the relevant Board of Examiners.

ON CAMPUS
TypeDescriptionValue
AssignmentTeam based software prototype15%
ProjectCompleted software project25%
Examination ^End of semester examination60%
ONLINE
TypeDescriptionValue
AssignmentTeam based software prototype15%
ProjectCompleted software project25%
Examination ^End of semester examination60%

^ Mandatory to Pass

Text References

  • ^ Schach, S. (2010). Object oriented and classical software engineering (8th ed.). Boston, MA: McGraw Hill.
  • Douglass, B. (2000). Real-time UML (2nd ed.). Reading, MA: Addison Wesley.
  • Booch, G., Maksimchuk, R.A., Engel, M.W., & Young, B.J. (2007). Object-oriented analysis and design with applications (3rd ed.). Reading, MA: Addison Wesley.
  • Arlow, J., & Neustadt, I. (2005). UML 2 and the unified process (2nd ed.). Reading, MA: Addison Wesley.
  • Binder, R. (2000). Testing object-oriented systems - models, patterns, and tools. Reading, MA: Addison-Wesley.

^ Mandatory reference


Disability Standards for Education (Commonwealth 2005)

For the purposes of considering a request for Reasonable Adjustments under the Disability Standards for Education (Commonwealth 2005), inherent requirements for this subject are articulated in the Unit Description, Learning Outcomes and Assessment Requirements of this entry. The University is dedicated to provide support to those with special requirements. Further details on the support for students with disabilities or medical conditions can be found at the Access and Inclusion website.

Academic Misconduct

Edith Cowan University has firm rules governing academic misconduct and there are substantial penalties that can be applied to students who are found in breach of these rules. Academic misconduct includes, but is not limited to:

  • plagiarism;
  • unauthorised collaboration;
  • cheating in examinations;
  • theft of other students' work;

Additionally, any material submitted for assessment purposes must be work that has not been submitted previously, by any person, for any other unit at ECU or elsewhere.

The ECU rules and policies governing all academic activities, including misconduct, can be accessed through the ECU website.

CSI6109|1|2