IS5411 Chap.2 Framing a Real Information Systems Project
Framing a Real Information Systems Project
Access 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. A contact provides evidence about the current process, its exceptions and the people responsible. The proposal is therefore not a product pitch.
It is an initial, reviewable account of an organisation and a problem the team can continue to investigate.
Two candidates test early commitment
The proposal presents two candidate projects, each with organisational background, a business problem, a proposed system and an explanation of how the proposal addresses the need. A preliminary use-case list makes the boundary visible.
One candidate is chosen after review, so feasibility, access and modelling depth can be compared before the team commits to detailed work.
Scope follows evidence
A project should be substantial enough to support analysis and modelling but bounded enough to complete. Functions arise from user goals and business events rather than from a desired count.
Each proposed capability should later reappear in use cases, processing, remembered information and review evidence. Capabilities that vanish were probably empty language; later functions with no proposal source may represent uncontrolled growth.
What this chapter covers
- 01
Real organisations
- 02
Accessible contacts
- 03
Business problems
- 04
Candidate comparison
- 05
System capabilities
- 06
Project boundaries
- 07
Preliminary use cases
- 08
Proposal review
Worked example · free
Choose the investigable project
- 3Compare access to process evidence.
- 3Compare system boundaries and controllable actors.
- 2State the remaining uncertainty.
Key terms
- Business Problem
- A specific mechanism in current work that creates delay, error, cost or lost opportunity.
- Project Boundary
- The limit separating the process the team will analyse from its external environment.
- Client Contact
- An accessible person able to explain and verify the organisation's work.
- System Capability
- A bounded business response the proposed system is expected to provide.
- Scope Growth
- The addition of functions that cannot be traced to the approved problem and capability set.
- Proposal Review
- The early challenge to whether evidence, need, scope and proposed response support one another.
Framing a Real Information Systems Project FAQ
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.
Why propose two projects instead of one?
Two candidates force comparison of access, feasibility, business value and modelling depth. The team can expose weak evidence or an unmanageable boundary before becoming attached to one solution. Review then selects the candidate that can support accurate work through the offering.
How can I tell whether a project is too broad?
Ask whether the team can identify the controlling organisation, observe the process, name actors and events, and model the important functions within the available time. If critical rules belong to unreachable parties or the proposed system spans unrelated problems, narrow the boundary. Prefer a modest boundary supported by reachable evidence over an ambitious but unverifiable proposal.
Exam move
Draft two candidate proposals for the same broad domain. Compare them on access, problem specificity, boundary control and modelling depth. For the stronger candidate, trace each capability into a preliminary verb-noun use case. Remove any capability that cannot be supported by an observed problem or stakeholder goal.
Write a one-sentence causal chain for every retained capability: the current process produces a named consequence because of a particular mechanism, and the capability changes that mechanism. If the sentence depends on an assumption, turn the assumption into an investigation question and identify who can answer it.
Stress-test the boundary by naming an adjacent problem that the project will not solve and explaining why it belongs outside. Then imagine the first proposal review. Defend the real organisation, the contact's access to the process and the reason the work can support use-case, process and data models. Do not defend a project with enthusiasm or social importance alone.
A modest case with verifiable rules is stronger than a fashionable case whose controlling actors cannot be reached. Preserve rejected candidates and review comments because they explain later scope decisions when a stakeholder asks why an attractive feature is absent. Add a scope ledger with three columns: confirmed capability, supporting evidence and excluded neighbour.
This small record makes later changes visible and forces every addition to identify the problem it solves. Review it before each new model so a diagram does not quietly expand the approved project.
Working through Framing a Real Information Systems Project in IS5411? Sia is AskSia’s AI Information Technology tutor — ask any IS5411 Framing a Real Information Systems Project question and get a clear, step-by-step explanation grounded in how IS5411 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.