CSSE3002 Lecture Notes - Lecture 4: Requirements Analysis, Xojo, User Story
28 Jun 2018
School
Department
Course
Professor
Importance of Software Requirements and Managing the
Requirements (Guest Lecture)
Speaker’s Background: Started in the Aerospace Industry
Agile isn’t a funky new method, been using extreme programming & agile for software
development.
Agile must also specify requirements: as a mutual agreement between customer &
developers.
Will teach you how to: pick the appropriate method for the project that you’re working on.
These days: disappointed with the IT track record, having catastrophic failures in the
industry. (Even in critical systems such as train systems, health systems)
e.g.
-ICT report card – not getting better
-Agile approach: causing catastrophic failures (e.g. UK- 24B over the health system in
2010)
-It is getting worse that the government is saying that they don’t want to invest in IT
anymore, getting risky to fund IT people, hence we must try to change their minds,
taking this profession of IT
When speaker started in the industry: never had failures (why? contract, deliver on time,
budget, ROI)
Queensland Health Payroll
Best example of stupidity in IT
Costing economy money that we cannot afford, industry going backwards
Why?
Do things badly
Spend lots of money for a project and fails
Early life cycle: have requirements, but deficient in specifications
It is possible to use Artificial Intelligence (complex tools) to unpack the requirements
before starting to build
Systems created 30 years ago are badly documented
When building system, must know that there will be maintenance
Maintenance is hard (keeping operational 24/7, making changes)
Who worry about requirements?
Not just software engineers/technician, everybody does
People whose money is being invested
find more resources at oneclass.com
find more resources at oneclass.com
Document Summary
Agile isn"t a funky new method, been using extreme programming & agile for software development. Agile must also specify requirements: as a mutual agreement between customer & developers. Will teach you how to: pick the appropriate method for the project that you"re working on. These days: disappointed with the it track record, having catastrophic failures in the industry. (even in critical systems such as train systems, health systems) e. g. ict report card not getting better. Agile approach: causing catastrophic failures (e. g. uk- 24b over the health system in. It is getting worse that the government is saying that they don"t want to invest in it anymore, getting risky to fund it people, hence we must try to change their minds, taking this profession of it. When speaker started in the industry: never had failures (why? contract, deliver on time, budget, roi) Costing economy money that we cannot afford, industry going backwards. Spend lots of money for a project and fails.
