Unit 30 Application Development
Unit 30 Application Development
The documentation listed in the tasks will need to comply with the following:
This should be written in a concise, formal academic style using single spacing and font
size 12. You are required to make use of headings, paragraphs and subsections as
appropriate, and all work must be supported with research and referenced using the
Harvard referencing system. Please also provide a bibliography using the Harvard
referencing system. The recommended word limit is 2,000-2,500 words, although you will
not be penalised for exceeding the total word limit.
Unit Learning Outcomes
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.
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.
Scenario:
Airline reservation systems incorporate airline schedules, fare tariffs, passenger
reservations and ticket records. Let assume there is a website for Airline reservation that
will allow his administration to perform CRUD operations like Add a passenger reservation
or update passenger information etc.
Suppose you want to insert new passenger information in a “Passenger_info" table of an
"Airline Database". The Passenger_info table has an attributes Passenger_Name and NIC
and Contact_no.
Note: CRUD is an acronym for Create, Read, Update, and Delete. CRUD operations are
basic data manipulation for database
Task 1:
Your first task is to produce the software design documentation by analysing the issues in
the requirements specification and deduce from that an appropriate solution and identify
the initial requirements.
Using the method you think most appropriate produce a well-structured Software Design
Document that defines a proposed solution and includes: relevant details on
requirements, system analysis, system design, coding, testing and implementation.
A well-defined problem definition statement and a determination of any risks relating to
the successful completion of your application.
Next you need to justify your solution to the requirements of the problem specified and
your choice(s) of software development methodology by comparing the different
software development tools and techniques you have researched. Include in this your
research into the use of software development tools and techniques, clearly identifying
which you have selected for use in developing this application.
Task 2:
You now need to coordinate with the rest of your team on the next stage of the
application's development. Which is to produce a functional business application and the
relevant support documentation and then evaluate it.
To this end you now need to create a formal presentation that effectively reviews your
business application, problem definition statement, proposed solution and development
strategy.
Use this presentation as part of a peer-review and document any feedback given. Then
interpret your peer-review feedback and identify any relevant opportunities you have not
previously considered. Evaluate those opportunities (insights, ideas and improvements)
and justify why you choose to include or not include them in the development of your
business application.
After you have completed this and utilising any opportunities you may have identified as
beneficial develop a functional business application based on a specific Software Design
Document with supportive evidence of using the preferred tools, techniques and
methodologies. This will need an appropriate set of support documents.
You may wish to include screenshots, photographs and similar within this.
The final stage is the review of your whole process of developing the application. You
need to produce a critical evaluation of the strengths and weaknesses of your business
application and fully justify opportunities for improvement and further development.
Include in this a critical review of the design, development and testing stages of your
application. A review of the performance of your business application against the Problem
Definition Statement and initial requirements. Conclude your review by reflectively
discussing the risks to the development that you identified originally.
P1 Explore a business-
related problem and M1 Analyse a business related
produce a well-defined problem using appropriate
Problem Definition methods and produce a well- LO1 & LO2
Statement supported by a structured Software Design D1 Justify your
set of user and system Document that defines a solution to a business-
requirements. proposed solution and includes related problem and
relevant details on requirements, your preferred
P2 Determine any areas of system analysis, system design, software
risk related to the successfulcoding, testing and development
completion of your implementation. methodology, by
application. comparing between
the various software
LO2 Use design and development methodologies with tools and development tools
techniques associated with the creation of a business application and techniques
researched.
M2 Compare the differences
P3 Research the use of
between the various software
software development tools
development tools and
and techniques and identify
techniques researched and justify
any that have been selected
your preferred selection as well as
for the development of this
your preferred software
application.
development methodology.
P4 Create a formal
presentation that effectively D2 Evaluate any new
reviews your business insights, ideas or
M3 Interpret your peer-review
application, problem potential
feedback and identify
definition statement, improvements to your
opportunities not previously
proposed solution and system and justify the
considered.
development strategy. Use reasons why you have
this presentation as part of a M4 Develop a functional business chosen to include (or
peer-review and document application based on a specific not to include) them
any feedback given. Software Design Document with as part of this
supportive evidence of using the business application.
P5 Develop a functional
preferred tools, techniques and
business application with
methodologies.
support documentation
based on a specified
business problem.