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 Development Processes
  • Unit Code

    CSI6110
  • Year

    2016
  • Enrolment Period

    1
  • Version

    1
  • Credit Points

    20
  • Full Year Unit

    N
  • Mode of Delivery

    On Campus
    Online

Description

This unit details different forms of software development processes, including sequential, iterative and formal models as well as those approaches based on reusability. In addition, the unit covers method measurement and software estimation techniques, the use of software metrics and automated tool support. The unit also presents current issues in the discipline.

Equivalent Rule

Unit was previously coded CSI5203

Learning Outcomes

On completion of this unit students should be able to:

  1. Apply techniques to estimate software project costs, duration and effort.
  2. Identify software capability determination and evaluation techniques.
  3. Reflect on the need for measurement and software metric formulation and evaluation, and
  4. Research the processes involved in software development.
  5. Use automated tools to manage the software processes.

Unit Content

  1. Estimating software projects.
  2. Methods for comparing software methods.
  3. Software capability models, determination and evaluation.
  4. Software metrics.
  5. Software processes I sequential models.
  6. Software processes II iterative models.
  7. Software processes III reusable models.
  8. Software processes IV formal models.

Additional Learning Experience Information

The main mode of learning will be through lectures with follow-up practical sessions where case studies will be undertaken and the results evaluated in group discussions.

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
AssignmentCumulative workshop tasks15%
Case StudyTeam based software engineering case study35%
Examination ^End of semester examination50%
ONLINE
TypeDescriptionValue
AssignmentCumulative workshop tasks15%
Case StudyTeam based software engineering case study35%
Examination ^End of semester examination50%

^ Mandatory to Pass

Text References

  • ^ Sommerville, I. (2011). Software engineering (9th ed.). Reading, MA: Addison-Wesley.
  • Jones, C., Bonsignour, O. (2011). The economics of software quality. New York, NY: Addison-Wesley Professional.
  • Chemutiri, M. (2010). Mastering software quality assurance: best practices, tools and techniques for software developers. New York, NY: J. Ross Publishing.
  • Kirchner, C., Kopetz, R., & Moreau, P. (2007). Anti pattern matching. Berlin, Germany: Springer Berlin Heidelberg.
  • Duvall, P. M., Matyas, S., & Glover, A. (2007). Continuous Integration. New York, NY: Addison-Wesley Professional.

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

CSI6110|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 Development Processes
  • Unit Code

    CSI6110
  • Year

    2016
  • Enrolment Period

    2
  • Version

    1
  • Credit Points

    20
  • Full Year Unit

    N
  • Mode of Delivery

    On Campus
    Online

Description

This unit details different forms of software development processes, including sequential, iterative and formal models as well as those approaches based on reusability. In addition, the unit covers method measurement and software estimation techniques, the use of software metrics and automated tool support. The unit also presents current issues in the discipline.

Equivalent Rule

Unit was previously coded CSI5203

Learning Outcomes

On completion of this unit students should be able to:

  1. Apply techniques to estimate software project costs, duration and effort.
  2. Identify software capability determination and evaluation techniques.
  3. Reflect on the need for measurement and software metric formulation and evaluation, and
  4. Research the processes involved in software development.
  5. Use automated tools to manage the software processes.

Unit Content

  1. Estimating software projects.
  2. Methods for comparing software methods.
  3. Software capability models, determination and evaluation.
  4. Software metrics.
  5. Software processes I sequential models.
  6. Software processes II iterative models.
  7. Software processes III reusable models.
  8. Software processes IV formal models.

Additional Learning Experience Information

The main mode of learning will be through lectures with follow-up practical sessions where case studies will be undertaken and the results evaluated in group discussions.

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
AssignmentCumulative workshop tasks15%
Case StudyTeam based software engineering case study35%
Examination ^End of semester examination50%
ONLINE
TypeDescriptionValue
AssignmentCumulative workshop tasks15%
Case StudyTeam based software engineering case study35%
Examination ^End of semester examination50%

^ Mandatory to Pass

Text References

  • ^ Sommerville, I. (2011). Software engineering (9th ed.). Reading, MA: Addison-Wesley.
  • Jones, C., Bonsignour, O. (2011). The economics of software quality. New York, NY: Addison-Wesley Professional.
  • Chemutiri, M. (2010). Mastering software quality assurance: best practices, tools and techniques for software developers. New York, NY: J. Ross Publishing.
  • Kirchner, C., Kopetz, R., & Moreau, P. (2007). Anti pattern matching. Berlin, Germany: Springer Berlin Heidelberg.
  • Duvall, P. M., Matyas, S., & Glover, A. (2007). Continuous Integration. New York, NY: Addison-Wesley Professional.

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

CSI6110|1|2