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

    Component Based Software Engineering
  • Unit Code

    CSI3303
  • Year

    2016
  • Enrolment Period

    1
  • Version

    1
  • Credit Points

    15
  • Full Year Unit

    N
  • Mode of Delivery

    On Campus
    Online

Description

This unit introduces component-based software engineering by examining various client/server and distributed architectures as well as associated frameworks. The unit also covers the practical and economic aspects of delivering component-based enterprise systems. In addition, standards and protocols for Web-based components are evaluated and used to implement applications.

Prerequisite Rule

Students must pass 1 units from CSI2343, CSP2104

Learning Outcomes

On completion of this unit students should be able to:

  1. Analyse various distributed architectures.
  2. Assure quality by identifying patterns in software products.
  3. Identify and document common problems in the implementation of component-based systems.
  4. Prepare appropriate deliverables for different stages of a component-based project.

Unit Content

  1. Component technologies.
  2. Component-based software engineering.
  3. Design patterns.
  4. Distributed architectures.
  5. Emerging issues in component-based software engineering.
  6. Legal and economic aspects of components.
  7. Object-oriented modelling.
  8. Web-based architectures.
  9. Web-based components.

Additional Learning Experience Information

Lectures, workshops and group activities.

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
AssignmentSoftware specification document15%
AssignmentSoftware Implementation35%
Examination ^End of semester examination50%
ONLINE
TypeDescriptionValue
AssignmentSoftware specification document15%
AssignmentSoftware Implementation35%
Examination ^End of semester examination50%

^ Mandatory to Pass

Text References

  • Szyperski, C. (2002). Component software (2nd ed.). New York: ACM Press.
  • Sommerville, I. (2007). Software engineering (8th ed.). New York: Pearson Education Limited.
  • Seely, S. (2002). SOAP: Cross platform web service development using XML. Upper Saddle River, NJ: Prentice Hall.
  • Metsker, S.J. and Wake, W.C. (2006). Design Patterns in Java. Boston, MA: Addison-Wesley. Note: Recommended text book, though not mandatory.
  • Heineman, G.T., & Councill, W.T. (2001). Component-based software engineering. New York: Addison-Wesley.
  • Cooper, J.W. (2000). Java design patterns: a tutorial. Reading, MA: Addison-Wesley.
  • Horstmann, C. (2004). Object-Oriented Design & Patterns. Upper Saddle River, NJ: Prentice Hall.

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.

CSI3303|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

    Component Based Software Engineering
  • Unit Code

    CSI3303
  • Year

    2016
  • Enrolment Period

    2
  • Version

    1
  • Credit Points

    15
  • Full Year Unit

    N
  • Mode of Delivery

    On Campus
    Online

Description

This unit introduces component-based software engineering by examining various client/server and distributed architectures as well as associated frameworks. The unit also covers the practical and economic aspects of delivering component-based enterprise systems. In addition, standards and protocols for Web-based components are evaluated and used to implement applications.

Prerequisite Rule

Students must pass 1 units from CSI2343, CSP2104

Learning Outcomes

On completion of this unit students should be able to:

  1. Analyse various distributed architectures.
  2. Assure quality by identifying patterns in software products.
  3. Identify and document common problems in the implementation of component-based systems.
  4. Prepare appropriate deliverables for different stages of a component-based project.

Unit Content

  1. Component technologies.
  2. Component-based software engineering.
  3. Design patterns.
  4. Distributed architectures.
  5. Emerging issues in component-based software engineering.
  6. Legal and economic aspects of components.
  7. Object-oriented modelling.
  8. Web-based architectures.
  9. Web-based components.

Additional Learning Experience Information

Lectures, workshops and group activities.

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
AssignmentSoftware specification document15%
AssignmentSoftware Implementation35%
Examination ^End of semester examination50%
ONLINE
TypeDescriptionValue
AssignmentSoftware specification document15%
AssignmentSoftware Implementation35%
Examination ^End of semester examination50%

^ Mandatory to Pass

Text References

  • Szyperski, C. (2002). Component software (2nd ed.). New York: ACM Press.
  • Sommerville, I. (2007). Software engineering (8th ed.). New York: Pearson Education Limited.
  • Seely, S. (2002). SOAP: Cross platform web service development using XML. Upper Saddle River, NJ: Prentice Hall.
  • Metsker, S.J. and Wake, W.C. (2006). Design Patterns in Java. Boston, MA: Addison-Wesley. Note: Recommended text book, though not mandatory.
  • Heineman, G.T., & Councill, W.T. (2001). Component-based software engineering. New York: Addison-Wesley.
  • Cooper, J.W. (2000). Java design patterns: a tutorial. Reading, MA: Addison-Wesley.
  • Horstmann, C. (2004). Object-Oriented Design & Patterns. Upper Saddle River, NJ: Prentice Hall.

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.

CSI3303|1|2