The Tender Document You are required to produce a tender document for a specified software project. You can discuss ideas with your tutor or TA.The tender document must consist of the following: An...

The Tender Document
You are required to produce a tender document for a specified software project. You can

discuss ideas with your tutor or TA.The tender document must consist of the following:
An introduction
A project outline
A skills matrix
A project plan
A project costing
A risk analysis
An ethical assessment/statement
You will submit a suitably professional document by the end of week 12.
Academic Good Practice
Please note this is a group coursework, whilst students are expected and encouraged to

collaborate no part of the submission should be the work of another group or individual without

correct accreditation. Failure to accredit other contributions correctly is academic dishonesty

and your work will be referred for plagiarism.
The Software Project
As we are all aware, software applications are created to solve problems in our society or to

imporove on existing solutoins. You are tasked to come up with a problem in our society that

can be solved with a software application. You may focus on one particular topic area or attempt

something more inclusive the choice is yours. You must present your idea to the tutor for

approval before commencing part 2.
For part one, we are looking at your ability to conceptualise and describe a piece of software

appropriately as well as plan out the activities, identify the resources and analyse the risks and

ethical issues.
Once all ideas have been presented and approved, each group will design, implement and test

the idea in the second half of the module.
Therefore, when conceiving your idea, you need to think of something that could be completed

by a small team of developers in less than 6 weeks.
Part 2

This assignment is worth 40% of the module course work mark and assesses learning

outcomes:
2. SPECIFY AND PLAN A SOFTWARE

DEVELOPMENT PROJECT USING AN

APPROPRIATE SOFTWARE DEVELOPMENT

LIFE-CYCLE MODEL.
Application

Enquiry
Learning
3. ANALYSE, DESIGN, IMPLEMENT, TEST AND

DOCUMENT ONE OR MORE COMPONENTS OF

A SOFTWARE PRODUCT USING

APPROPRIATE SOFTWARE DEVELOPMENT

METHODS AND TOOLS.

Application

Communication
Problem Solving
ReflectionYour group task is to use software engineering principles to develop a software application to

solve the problem identified in part 1. In addition, you will produce a presentation (lasting no

more than 20 minutes) of your group work which you will deliver to the entire class in week

12.
You will submit a suitably professional document by the deadline stated in class.
For any of the software development life-cycle model chosen for the project, the following

software processes should be considered.
Software Requirement specification: Should define and classify requirements for the project.
• Should use requirement engineering process to obtain all needed software

requirements
Software Design: Should use at least four UML models to describe both structural (class,

component, object diagram, etc) and behavoir ( activity, state machine, use case, sequence

diagram, etc) of the system.

Software Development: Should use any of the high level programming languages to implement
software system.

Component,System and Acceptance Testing: Define policies for unit, system and acceptance

testing.
Evolution: Code should be well structured and well documented for future maintainability.
Both part 1 and part 2 document should not be less than 3000 thousand words.
Individuals in the group should also produce a reflective report detailing their contributions,

challenges and successes in the group. This report should be 10% or more of the group work.
Individual submission: -
• Reflective report.