Software Architecture

Syllabus

Learning Outcomes

Demonstrate an understanding of general systems theory to the design of information systems in organisations
Discuss the impact of organisational structure on the design of information systems
Explain the various stages and associated roles, of the traditional software development lifecycle from feasibility/investigation through end‐of‐ maintenance/support
Describe the role of modern methodologies in the software development process
Demonstrate an understanding of the management and technology issues, including risks and common pitfalls, involved in the design and construction of software systems
Use straightforward UML use‐case diagrams to depict the interaction between an actor and system
Engage a modern methodology to aid the design of a system from initial requirements
Apply the main tools and techniques used in the gathering, recording and analysis of information relating to an existing information system
Generate Java (or suitable Object‐ Oriented language) classes from UML class diagram specifications
Test the design specification of a new information system based on a provided use‐case
Explain the development of an information system using a traditional systems development life cycle model

Skills Demonstrations

There are seven Skills Demos in the form of assignments in this module
Each skills demo covers (primarily) one Learning Outcome
Each skills demo is weighted at 10%
The numbering of each skills Demo is not related to the learning outcome, nor is it related to the order of completion

The current order of completion for assessment for this course, at this time is:

Skills Demo 2

[LO4] Describe the role of modern methodologies in the software development process including

history and evolution of the Agile Software Development
principles of the Agile manifesto
the main Agile Software Development methods
advantages and disadvantages of Agile over Waterfall

Skills Demo 3

[LO8] Apply the main tools and techniques used in the gathering, recording and analysis of information relating to an existing information system such as:

Use cases
Interviews
Surveys
Observation
Document Analysis
Data gathering
Stakeholder analysis

Skills Demo 5

[LO6] Use UML use‐case diagrams to depict the interaction between an actor and system; include

actors
use cases
system boundary
relationships (include extend)

Skills Demo 6

[LO10] Test the design specification of a new information system based on a provided use‐case. Benefits of testing. Derive test case(s) from a provided use-case to include elements such as

actor
description
preconditions
postconditions
workflow
alternate/exception flows

Skills Demo 4

[LO9] Generate OOP classes from UML class diagram specifications:

elements of a class diagram
purpose and use, by whom
create a class diagram to model object(s)
use IDE to code and test the class(es)
discuss relationship between the class diagram and the code produced

Skills Demo 1

Cross Modular with PDP Team assignment

[LO7] Design and develop a piece of Software using an Agile Software Development Methodology.

Document the stages, processes, procedures, meetings and tools used from your chosen modern methodology in designing your piece of software

Skills Demo 7

Cross modular with Web Authoring Project

[LO11] Complete development using a traditional systems development life cycle model (waterfall)

outline the stages using this approach
For each stage in the methodology, explain the main activities that took place.

Exam (30%)

[LO1] Demonstrate an understanding of general systems theory to the design of information systems in organisations

[LO2] Discuss the impact of organisational structure on the design of information systems

[LO3] Explain the various stages and associated roles, of the traditional software development lifecycle from feasibility/investigation through end‐of‐ maintenance/support

[LO5] Demonstrate an understanding of the management and technology issues, including risks and common pitfalls, involved in the design and construction of software systems

Page updated

Google Sites

Report abuse