Applications Development Assignment
Applications Development Assignment
Unit Title Unit 30: Applications Development Batch No & Semester CSD 12 & 13, Semester 03
Please note that grade decisions are provisional. They are only confirmed once internal and external moderation
has taken place and grades decisions have been agreed at the assessment board.
LEARNER ASSESSMENT SUBMISSION AND DECLARATION
When submitting evidence for assessment, each learner must sign a declaration confirming that the work is
their own.
Please list the evidence submitted for each task. Indicate the page numbers where the evidence can be found
or describe the nature of the evidence (e.g. video, illustration).
Learner declaration
I certify that the work submitted for this assignment is my own. I have clearly referenced any sources used
in the work. I understand that false declaration is a form of malpractice.
Assignment Assessor
Grading Criteria Date Acheived Comments
No. Signature
Unit Review Plan ISVU 2014 Rev 1.0
Submission Format
Submission Format
The submission is in the form of two documents:
Part 1: IEEE Software Requirement Specification must be prepared and completed, template is
attached herewith the assignment
Part 2: Report 2000 to 3000 words, Analysis document on the development methodologies,
development tools and techniques
Part 3: System Presentation (Microsoft PowerPoint) report on functional business application,
filled peer evaluation sheet
Part 4: Code with comments, code snippets
Part 5: Submit your developed business application with the relevant supporting documentation
(user manuals etc.). As confirmation of self-development, source code and project files should be
zipped and provided as softcopy on CD
Part 6: Critical Software Quality Assurance Report
You are required to make use of headings, paragraphs, subsections and illustrations as
appropriate, and all work must be supported with research and referenced using the Harvard
referencing system.
Unit Learning Outcomes
LO1: Produce a Software Design Document by analyzing a business-related problem and deduce an
appropriate solution including a set of initial requirements.
LO2: Use design and development methodologies with tools and techniques associated with the
creation of a business application.
LO3: Work individually and as part of a team to plan and produce a functional business application
with support documentation.
LO4: Evaluate the performance of a business application against its Software Design Document and
initial requirements
The client wants to build a SaaS (Software as a Service) application to serve the local private hospitals where
the hospitals can list the specialists and manage them under their particular hospital.
On the other hand, a general public who requires the consultation of a medical practitioner wants to use a
mobile application to search a particular doctor / consultant based on the hospital and or specialization and or
date of consultation.
Considerations
• They require a cloud-based solution so that data can be shared across multiple deployment environment
(Web, Mobile & Etc)
• The client is more favourable towards a hybrid application as the budget is limited where the single
code based can be utilized for cross platform deployment.
• As a company you are expected to practice agile methodology to realize the solution.
• You're also expected to complete the project in 3 sprints (where each sprint is of 2 weeks). Thus, you
are expected to familiarize with the agile methodology and plan accordingly
• You're expected to identify at least 3 functional requirements in the web based application and at least
2 functional requirements in mobile app.
• You're allowed to make reasonable assumptions considering the best interest of the end users.
• Your planning should reflect almost equal responsibilities to each of your team members (for group
only).
• You are required to refer the existing samples and select tools and technologies appropriate to realize
the clients’ requirements.
Assignment Brief and Guidance
Part 1
Do an analysis of the scenario given with the real-world context to fill in gaps, use any form of data gathering techniques
that you have acquired from Unit 09 (SDLC), once the analysis is complete use the Software Specification Report to
produce a full detailed requirement specification, you may attach the samples of analysis data as evidence to the
appendix. Risk analysis should be included in the System Features (Functional Requirements) of your SRS
Part 2
Write a report researching into the relevant technologies, software tools, IDEs, programming methodologies and
development methodologies that are relevant to this application, you must compare these finding with other similar
technologies, software tools and methodologies. These must be compared and justified (you must continue with your
selected methodologies, tools and software in the next parts, therefore select carefully)
Part 3
You must prepare a presentation to pitch (present) your idea to others and the lecturer, your product idea will be rated
according to the peer evaluation sheet provided with this assessment. An individual report must be also submitted along
with this document describing the contributions done by you
Part 4
Develop application individually based on the original Software Specification from Part 1, comments, important
algorithms should be extracted as code snippets and explained
Part 5
You must submit your developed application which you will develop based on the selected methodology, tools and
techniques identified in part 2, and according to the specifications analyzed in part 1, provide the relevant user
manuals etc.
Part 6
Critically review and produce a quality assurance report for the application that you have developed with key areas
that focus on how your application has addressed the relevant user requirements, include any development pitfalls
and other issues that were encountered
Learning Outcomes and Assessment Criteria
LO1 Produce a Software Design Document by analysing a business-related problem and deduce an
appropriate solution including a set of initial requirements
LO2 Use design and development methodologies with tools and techniques
associated with the creation of a business application
P3 M2
Research the use of software Compare the differences between the
development tools and techniques and various software development tools and
identify any that have been selected for techniques researched and justify your
the development of this application. preferred selection as well as your
preferred software development
methodology.
LO3 Work individually and as part of a team to plan and produce a functional business application with
support documentation
P4 M3 D2
Create a formal presentation that Interpret your peer-review feedback and
Evaluate any new insights, ideas or
effectively reviews your business identify opportunities not previously
potential improvements to your
application, problem definition considered. system and justify the reasons why
statement, proposed solution and you have chosen to include (or not to
development strategy. Use this M4 include) them as part of this business
presentation as part of a peer-review
Develop a functional business application.
and document any feedback given. application based on a specific Software
Design Document with supportive
P5 evidence of using the preferred tools,
Develop a functional business techniques and methodologies.
application based on a specified
business problem.
LO4 Evaluate the performance of a business application against its Software Design Document and initial
requirements
P6 M5 D3
Review the performance of your Analyse the factors that influence the Critically evaluate the strengths and
business application against the performance of a business weaknesses of your business
application and fully justify
Problem Definition Statement and application and use them to
opportunities for improvement and
initial requirements. undertake a critical review of the further development.
design, development and testing
stages of your application. Conclude
your review by reflectively
discussing your previously identified
risks