IS5411 Systems Analysis and Design
IS5411 Overview
- City University of Hong Kong
- Semester A, 2026/27
- Postgraduate course
- Closed-book final examination
- Two-hour examination
What the course asks you to do
Systems analysis establishes the outcomes and behaviour an information system must deliver; systems design describes in detail the solution that will meet that need. IS5411 develops both abilities through modelling, requirements investigation and a team project grounded in a real organisation.
- Assessment Coursework and examination each carry half of the published grade, and both halves must be passed.
- Exam focus Small case studies test conceptual understanding together with the ability to construct and defend models.
- Core method Trace the business problem into events, use cases, remembered things and messages across the system boundary.
What you get in the full IS5411 Exam Bible
- 8 chapters, 37 pages — every examinable topic
- 22 original practice questions, each with a model answer in the Final Examination format
- 8 worked examples, solved the way IS5411 marks
- 8 computed figures, redrawn from the course’s own numbers
- Exam-morning plan for the Final Examination (50%) — what to revise last, where marks are lost
Free on this page: assessment table, chapter map, one worked example, key terms, FAQ. The rest is in the full exam bible.
How IS5411 is assessed
| Component | Weight | Format |
|---|---|---|
| Continuous Assessment | 15% | Class and lab participation, applied analysis techniques and submitted modelling exercises |
| Project Presentation | 10% | Team presentation of draft project work and discussion |
| Project | 25% | Team requirements gathering and modelling project |
| Final Examination | 50% | Two-hour closed-book examination using one or more small case studies |
The four numeric components total 100%. The official current catalogue confirms a 50% coursework and 50% examination split, a two-hour closed-book final using one or more small case studies, and the requirement to pass both coursework and examination. The pass condition applies to the coursework half and examination half rather than to one assessment row alone.
Assessment structure
The segment widths reproduce the published weights and total one hundred per cent.
What other students are asking about IS5411
- Where can I find lecture notes or study guides for IS5411 at CityU?
- The IS5411 study guide in AskSia Library covers Systems Analysis and Design in 8 chapters, with the assessment table, a chapter-by-chapter topic map, key terms and a worked example, free to read on this page.
- Is there a final exam in IS5411, and how much is it worth?
- Yes. In the offering this AskSia Library guide is built from, Final Examination carries 50% of the IS5411 mark; the full split is Continuous Assessment 15%, Project Presentation 10%, Project 25%, Final Examination 50%.
- What does IS5411 cover on framing a real information systems project?
- In AskSia Library's IS5411 guide, the Framing a Real Information Systems Project chapter explains real organisations, business problems, feasible boundaries and proposal review.
- What does IS5411 cover on interviewing and investigating requirements?
- In AskSia Library's IS5411 guide, the Interviewing and Investigating Requirements chapter explains questions, examples, exceptions, workflow evidence and validation.
- What does IS5411 cover on functional requirements and business processes?
- In AskSia Library's IS5411 guide, the Functional Requirements and Business Processes chapter explains functional and non-functional requirements, elementary processes and stable results.
Current IS5411 dates
| Date | Item | Control |
|---|---|---|
| 15 or 18 September 2026 | Team contract | The class section determines the published deadline. |
| 6 or 9 October 2026 | Group project proposal | The class section determines the published deadline. |
| 6 or 9 October 2026 | Noun-technique assignment | The class section determines the published deadline. |
Dates are as published in the current course lab slides for Semester A, 2026/27. Confirm exact deadlines and submission settings in the live LMS.
What IS5411 covers
The chapters follow the dependency from project framing and requirements investigation through use cases, domain classes and system sequence diagrams.
Systems Analysis and the Development Lifecycle
business need, analysis, design, testing, deployment and feedbackAnalysis and design answer different questions
Systems analysis identifies the outcomes and behaviour an information system must deliver. Systems design defines the detailed solution that will satisfy that need.
- Analysis versus design
- System vision
- Project planning
- Fact-finding
- Use cases and classes
- Database and interface design
Framing a Real Information Systems Project
real organisations, business problems, feasible boundaries and proposal reviewAccess makes a project investigable
The group project must respond to an evidenced organisational problem or opportunity within a real organisation that the team can access.
- Real organisations
- Accessible contacts
- Business problems
- Candidate comparison
- System capabilities
- Project boundaries
Interviewing and Investigating Requirements
questions, examples, exceptions, workflow evidence and validationQuestions should change the model
Requirements interviews are structured investigations, not conversations about preferred features. Preparation identifies the process, current evidence and uncertainties that matter.
- Interview purpose
- Question design
- Recent examples
- Exception probes
- Actors and hand-offs
- Workflow decisions
Functional Requirements and Business Processes
functional and non-functional requirements, elementary processes and stable resultsFunctions and qualities are separate claims
Functional requirements describe activities the system must perform, often represented as use cases.
- Functional requirements
- FURPS+ qualities
- Elementary processes
- Business events
- Stable states
- Verb-noun names
Events and Use Case Discovery
user goals, CRUD, external events, temporal events and state eventsDiscovery needs several starting points
User-goal analysis begins with potential users and the tasks they seek to accomplish. Event decomposition begins with occurrences that require a response.
- User categories
- User goals
- CRUD coverage
- External events
- Temporal events
- State events
Use Case Descriptions and Diagrams
description depth, actors, automation boundaries and include relationshipsDescriptions carry processing detail
Brief, intermediate and fully developed descriptions represent increasing detail about one system response.
- Brief descriptions
- Intermediate flows
- Fully developed flows
- Primary actors
- Automation boundaries
- Include relationships
Domain Classes and Relationship Models
noun classification, association classes, multiplicities and inheritanceThe noun technique starts a decision process
Nouns from use cases, actors, inputs, outputs and documents are candidate classes, not automatic tables.
- Noun extraction
- Include decisions
- Exclude decisions
- Attributes and types
- Association classes
- Whole-part relationships
System Sequence Diagrams
black-box systems, ordered messages, conditions, repetition and returnsThe system remains one black box
A system sequence diagram shows ordered input and output messages for one use-case scenario. External actors have lifelines and the entire system appears as one object.
- Actor lifelines
- Black-box systems
- Input messages
- Return messages
- Time order
- Conditions
The official course aims place structured and object-oriented tools side by side, with attention to processes, use cases, data structures, system objects, files, inputs, outputs and program specifications.
The available teaching sequence concentrates on the analytical models that make later design reviewable.
Why the models belong together
A useful answer begins with a business event and the actor who needs a result. User-goal and event analysis discover use cases. Written descriptions reveal the main flow, alternatives and stable outcomes.
Domain class models identify the things and relationships the system must remember. System sequence diagrams then show the messages that cross the automation boundary while keeping internal design hidden.
Each view should expose a different part of the same requirement and should agree with the others.
How the assessment shapes revision
The published structure assigns half the grade to continuous assessment, project presentation and the group project, and half to a two-hour closed-book final examination. Both coursework and examination must be passed.
The final uses one or more small case studies to assess conceptual understanding and modelling skills. That description rewards precise distinctions, correct directionality and models whose elements can be justified from case facts. It does not publish a question count or detailed paper structure, so this guide practises transferable case analysis rather than a guessed format.
Worked example · free
Choose the model that answers the question
- 3Name the review question and select the matching model.
- 3Identify the actors, goals and boundary evidence.
- 2State what detail belongs in a later model.
Key terms
- Systems Analysis
- The activities used to establish the outcomes and behaviour an information system must deliver.
- Systems Design
- The activities used to define and describe the system that will solve an established need.
- Functional Requirement
- An activity the system must perform for a user or business process.
- Elementary Business Process
- A meaningful task that one person performs in one place and time, producing value and a stable state.
- User Goal
- A business result an actor seeks when interacting with the system.
- External Event
- An occurrence outside the system that requires a system response.
- Temporal Event
- An occurrence triggered when a defined point in time is reached.
- State Event
- An internal condition change that requires the system to respond.
- Automation Boundary
- The line separating the computerised system response from external actors and work.
- Domain Class
- A distinct thing in the problem domain about which the system must preserve information.
- Association Class
- A class that stores attributes belonging to a many-to-many relationship.
- System Sequence Diagram
- A UML interaction view showing ordered messages between external actors and the system as one black box.
IS5411 FAQ
How is the course assessed?
The published structure is Continuous Assessment at fifteen per cent, Project Presentation at ten per cent, Project at twenty-five per cent and Final Examination at fifty per cent. The current catalogue confirms that coursework and examination each make up half of the grade, and the numeric components total one hundred per cent.
Do I have to pass the final examination separately?
Yes. The official course information states that coursework and the examination must both be passed to receive an overall pass. Treat the two halves as separate requirements when planning revision; a strong result in one half does not remove the requirement attached to the other.
What is published about the final examination?
The final is described as a two-hour closed-book examination assessing conceptual understanding and modelling skill through one or more small case studies. The available course information does not publish sections or per-question marks, so prepare the model-selection and justification process rather than assuming a paper layout.
Which requirements technique should I use first?
Start from the evidence you have, then cross-check with the other techniques. User goals are direct when actors can state their tasks, event decomposition broadens coverage across external, temporal and state triggers, and CRUD analysis tests whether the discovered functions manage remembered information completely.
When is a noun a domain class?
Include a noun when it represents a distinct in-scope thing with multiple instances and meaningful attributes or relationships that the system must remember. Exclude the system itself, actions, outputs, examples, duplicate names and values better treated as attributes. Use further research only for a precise unresolved question.
What belongs on a system sequence diagram?
Show external actors, the system as one black-box object, and ordered input and return messages for one scenario. Leave databases, controllers and internal components out because they answer design questions. Conditions and loops belong only when the validated use-case flow requires them.
Are past examination papers included in the course information used here?
The available teaching information does not contain a past final paper, sample examination, solution or published per-question marking scheme. Practice in this guide is independently authored from the modelling moves used in lectures and labs, and any displayed marks are AskSia study allocations.
Questions students ask in each IS5411 chapter
- Why must analysis come before detailed design?
- Analysis establishes the behaviour and information the business needs, while design chooses how to realise them. Starting with a platform or interface can hide disagreements about the work itself. A stable requirement lets several designs be compared against the same business result. Chapter 01 · Systems Analysis and the Development Lifecycle
- Why does the project need a real organisation?
- A real organisation supplies people and processes the team can investigate, including exceptions and informal workarounds that a hypothetical case would invite the team to invent. Access lets stakeholders challenge the problem, boundary and proposed capabilities before detailed models are produced. Chapter 02 · Framing a Real Information Systems Project
- What makes an interview question useful?
- A useful question produces evidence that changes or confirms a model. It identifies a step, rule, actor, input, output or exception. Questions that merely invite agreement with a proposed design test the analyst's idea rather than investigating the participant's work. Chapter 03 · Interviewing and Investigating Requirements
- How do functional and non-functional requirements differ?
- Functional requirements state the activities the system performs. Non-functional requirements state qualities or constraints such as reliability, security and response performance. A quality should qualify an identified behaviour, while the behaviour can be reviewed without assuming one technical implementation. Chapter 04 · Functional Requirements and Business Processes
- Which use-case discovery technique is most complete?
- Event decomposition offers broad coverage because it includes external, temporal and state triggers, but users and data can still reveal gaps. Combine it with user-goal interviews and CRUD analysis. The techniques are valuable because their blind spots differ, not because one replaces the others. Chapter 05 · Events and Use Case Discovery
- When should a use case be fully developed?
- Use the full form when detailed rules, alternatives and outcomes are needed for modelling or design. Early in discovery, brief descriptions are cheaper and easier to revise. Increase detail in response to questions the current model cannot answer rather than completing every field automatically. Chapter 06 · Use Case Descriptions and Diagrams
- Should every noun become a class?
- No. Nouns are candidates that must pass the memory test. Exclude the system, interfaces, actions, outputs, synonyms, examples and values better represented as attributes. Include distinct in-scope things with repeated instances and their own meaningful attributes or relationships. Chapter 07 · Domain Classes and Relationship Models
- Why are databases omitted from a system sequence diagram?
- The diagram models the observable interaction contract between external actors and the system as one object. A database is an internal design component. Showing it opens the black box and answers a different question about implementation rather than required boundary messages. Chapter 08 · System Sequence Diagrams
How to study for the exam
Carry one original service case through the whole guide. Begin by stating the business problem and automation boundary in plain language. Build a use-case catalogue from user goals and events, then challenge it with CRUD questions. Write one fully developed use-case description with a main flow, an exception and stable outcomes.
Derive a domain model by defending each included noun and reading every multiplicity in both directions. Finish with a system sequence diagram that keeps the system black-boxed and shows the outputs the actor needs.
After each model, reconcile it with the earlier views: every outcome should have a durable representation, every actor decision should cross the boundary visibly, and every line should be explainable from a case fact. For closed-book revision, practise this sequence on short unfamiliar cases and use a fixed final audit for boundaries, arrow direction, multiplicities and missing alternatives.
Your AI Information Technology tutor for IS5411
Stuck on a hard IS5411 question? Sia is AskSia’s AI Information Technology tutor — ask any IS5411 Systems Analysis and Design question and get a clear, step-by-step explanation grounded in how the course is actually taught and assessed. Read this whole study guide free, then take your hardest questions to Sia.