1. Home
  2. Software and Systems Management [CSI5202]

School: 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 and Systems Management

  • Unit Code

    CSI5202

  • Year

    2016

  • Enrolment Period

    1

  • Version

    1

  • Credit Points

    20

  • Full Year Unit

     N

  • Mode of Delivery

    On Campus
    Online

Description

This unit introduces models that provide a powerful means of reflecting on and examining phenomena in software development. This is done by using systems modelling and systems thinking as a means of managing the software development process. A CASE tool is used to demonstrate these ideas on topics such as Software Development Methodologies, project planning and control, productivity and effectiveness, management models and project management.

Learning Outcomes

On completion of this unit students should be able to:

  1. Assess the effectiveness and potential of applying systems modelling to software engineering and software management.
  2. Critique a range of systems modelling techniques.
  3. List systems concepts, systems thinking and systems models and explain the significance of systems ideas in software engineering and software management.
  4. Utilise and apply a range of systems-oriented Development Methodologies.

Unit Content

  1. Causal loop modelling.
  2. Dynamic modelling.
  3. Organisational learning.
  4. Socio-technical analysis.
  5. Soft Systems methodology.
  6. Strategic Options Development Analysis.
  7. Strategic choice method.
  8. Systems thinking.
  9. Viable systems methodology.

Additional Learning Experience Information

Lectures, workshops and exercises.

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
AssignmentExercises 30%
AssignmentReport 30%
ExaminationExamination 40%

Text References

  • ^ Maani, K.E. and Cavana, R.Y. (2007). Systems Thinking, Systems Dynamics: Managing change and complexity (2nd ed.). Auckland, New Zealand: Pearson Education.
  • Sallis, P.J., Tate, G., & MacDonnell, S.G. (1995). Software engineering. Practice, management and improvement. Sydney: Addison-Wesley.
  • Pressman, R.S. (1982). Software engineering - A practitioner's approach. New York: McGraw-Hill.
  • Humphrey, W.S. (1990). Managing the software process. Reading, Massachusetts: Addison-Wesley.
  • Gilb, T. (1988). Principles of software engineering management. Wokingham, England: Addison-Wesley.
  • Daniels, N.C. (1994). Information technology.The management challenge. Wokingham, England: Addison-Wesley.
  • Checkland, P.B., & Scholes, J. (1991). Soft systems methodology in action. Chichester: John Wiley & Sons.
  • Checkland, P.B. (1990). Systems thinking, systems practice. Chichester: John Wiley & Sons.
  • Brooks, F.P. (1975). The mythical man-month. Reading, Massachusetts: Addison-Wesley.
  • Boehm, B.W. (1981). Software engineering economics. Englewood Cliffs, New Jersey: Prentice-Hall.
  • Yourdon, E. (Ed.). (1982). Writing of the revolution. New York: Yourdon Press.
  • De Marco, T. (1982). Controlling software projects. New York: Yourdon Press.

^ 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.

CSI5202|1|1

School: 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 and Systems Management

  • Unit Code

    CSI5202

  • Year

    2016

  • Enrolment Period

    2

  • Version

    1

  • Credit Points

    20

  • Full Year Unit

     N

  • Mode of Delivery

    On Campus
    Online

Description

This unit introduces models that provide a powerful means of reflecting on and examining phenomena in software development. This is done by using systems modelling and systems thinking as a means of managing the software development process. A CASE tool is used to demonstrate these ideas on topics such as Software Development Methodologies, project planning and control, productivity and effectiveness, management models and project management.

Learning Outcomes

On completion of this unit students should be able to:

  1. Assess the effectiveness and potential of applying systems modelling to software engineering and software management.
  2. Critique a range of systems modelling techniques.
  3. List systems concepts, systems thinking and systems models and explain the significance of systems ideas in software engineering and software management.
  4. Utilise and apply a range of systems-oriented Development Methodologies.

Unit Content

  1. Causal loop modelling.
  2. Dynamic modelling.
  3. Organisational learning.
  4. Socio-technical analysis.
  5. Soft Systems methodology.
  6. Strategic Options Development Analysis.
  7. Strategic choice method.
  8. Systems thinking.
  9. Viable systems methodology.

Additional Learning Experience Information

Lectures, workshops and exercises.

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
AssignmentExercises 30%
AssignmentReport 30%
ExaminationExamination 40%

Text References

  • ^ Maani, K.E. and Cavana, R.Y. (2007). Systems Thinking, Systems Dynamics: Managing change and complexity (2nd ed.). Auckland, New Zealand: Pearson Education.
  • Yourdon, E. (Ed.). (1982). Writing of the revolution. New York: Yourdon Press.
  • Sallis, P.J., Tate, G., & MacDonnell, S.G. (1995). Software engineering. Practice, management and improvement. Sydney: Addison-Wesley.
  • Pressman, R.S. (1982). Software engineering - A practitioner's approach. New York: McGraw-Hill.
  • Gilb, T. (1988). Principles of software engineering management. Wokingham, England: Addison-Wesley.
  • Daniels, N.C. (1994). Information technology.The management challenge. Wokingham, England: Addison-Wesley.
  • Checkland, P.B., & Scholes, J. (1991). Soft systems methodology in action. Chichester: John Wiley & Sons.
  • Checkland, P.B. (1990). Systems thinking, systems practice. Chichester: John Wiley & Sons.
  • Brooks, F.P. (1975). The mythical man-month. Reading, Massachusetts: Addison-Wesley.
  • Boehm, B.W. (1981). Software engineering economics. Englewood Cliffs, New Jersey: Prentice-Hall.
  • Humphrey, W.S. (1990). Managing the software process. Reading, Massachusetts: Addison-Wesley.
  • De Marco, T. (1982). Controlling software projects. New York: Yourdon Press.

^ 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.

CSI5202|1|2