FIT4004 Lecture Notes - Lecture 1: Acceptance Testing, Learning Management System, Mobile App
Week 1
Question 1
A. The control system for the landing module of an uncrewed scientific space probe to
Mars.
●Functionality - 5
○A lot of money is going into this, so it needs to do what it’s meant to do to
avoid catastrophic consequences.
●Reliability - 5
○Need to ensure that all aspects of the module is reliable in the sense that
it is robust and there are no major flaws or there will be a massive debt
otherwise
●Usability - 3
○Important in emergency situations when users might be panicking, but
otherwise can be sacrificed for the sake of the other quality property
seeing as only trained professionals would have access to using it.
●Efficiency - 4
○The landing module will have a rather small memory, so the efficiency of
the control system is important for the module
●Maintainability - 4
○Relatively short term project use after development
○But for the effort that goes into it, it should have some level of
maintainability
●Portability - 2
○Not that important since the system only works on the probe, but still
have a chance to be transferred to another similar probe
B. A learning management system similar to Moodle.
●Functionality - 4
○Failure of functionality will not result to dire consequences, there’s always
the option to talk to faculty members to get information
●Reliability - 3
○You definitely want to be able to rely on it when it comes to assignment
submissions and important assessments, but if it doesn’t work then it’s
probably a minor inconvenience at most.
●Usability - 5e
○Have a wide range of users(teachers, students) with different
backgrounds, therefore need it to be usable by everyone
●Efficiency - 3.5
○Large volumes of users
○If this is the only tool then users will have no other choice other than to
wait however inefficient
●Maintainability - 5
○Frequent updates
●Portability - 4
○The more user a system has, the portable it needs to be as different users
may have different needs and you need cater to all or at least most
C. A mobile app that morphs pictures of people with pictures of cute cats.
●Functionality - 3
○If the app doesn’t morph it’s not going to cause bad consequences its just
a fun app
●Reliability - 2
○It’s just for fun
●Usability - 4.5
○Due to the possible young target audience you’d want it to be fairly easy
●Efficiency - 3
○If it only has a simple function, you don’t want to waste time and
computer resources for it.
●Maintainability - 2
○Not as important. I don’t see major extension to this app
●Portability - 4
○Mobile app must be able work on android and Ios
Question 2
In the Queensland Health payroll system (link on Moodle), User Acceptance Testing
(testing conducted on the complete system before it was rolled out to users) revealed
that the product had "thousands of defects". If the advice of the test engineer had been
followed and rollout had been delayed until the identified faults had been rectified,
would this have been a satisfactory SQA process?
Take about 15 minutes to analyse the strengths and weaknesses of such an SQA
process, considering both the final product and the resources required to deliver it.
Strengths
●Having a test engineer to use an expert
Weaknesses
●QA testing must happen throughout developing a system not just at the end
●Better to little bit of time rectifying defects rather than failed project, wasting all
resources on project and starting again.
●Should do all sorts of other testing before user acceptance testing
Question 3
Think about the following types of artifacts created during a software development
project. Classify them as informal, formal, or executable, and briefly explain why:
●Source code
○Executable
○Code can be run
●A "storyboard" depicting the flow between screens based on user input in a
mobile app
○Formal/Informal - depends on team/project
● A properly-formed UML state diagram.
○Formal
○It’s detailed and can be relied upon during the development stage
○Has formal syntax
●A partial UML class diagram on a whiteboard.
○Informal
○Partial, doesn’t have all the notation done possibly (?)
●A pseudocode description of the algorithm to be implemented in a method
○inFormal
Document Summary
Question 1: the control system for the landing module of an uncrewed scientific space probe to. A lot of money is going into this, so it needs to do what it(cid:519)s meant to do to avoid catastrophic consequences. Need to ensure that all aspects of the module is reliable in the sense that it is robust and there are no major flaws or there will be a massive debt otherwise. Important in emergency situations when users might be panicking, but otherwise can be sacrificed for the sake of the other quality property seeing as only trained professionals would have access to using it. The landing module will have a rather small memory, so the efficiency of the control system is important for the module. Relatively short term project use after development. But for the effort that goes into it, it should have some level of maintainability.