You are working for a company that specialises in bespoke software development. The company has been asked by a recruitment agency to develop an application that would enable job-seekers to fill their CV online in a structured way. The application would enable the agency to search the CVs to find job-seekers with a particular qualification, skill or experience.
One of your company’s analyst has interviewed several people in the agency in order to come up with a database design that captures the sort of data the agency would like in the job-seekers’ CV. He then went on to implement the design in MySQL in order to build a prototype application to test the design. However, before he could do this he suddenly left the company and left no documentation.
Your manager has decided to allocate a small team of programmers to build the prototype based on using MySQL database, and make sure all documentations are up-to-date. You are one of the members of this team. She has advised you that it would be a good idea to create a new database design in order to understand it better. She has also advised you that you should investigate and evaluate any software engineering tools that could help you with this and similar future projects.
You have been asked to produce a report (required content is specified below) and work in a team to prepare a demo & presentation for the client.
Your team will be developing a prototype that would
- Enable job-seekers to enter and edit their CV online
- Enable agency employees to search for job-seekers with a particular qualification, skill or experience
- Calculate Halstead’s volume on your code and present it to stake holders for KPIs.
Individual Report Content
The report should contain the following:
● Brief summary of the software engineering tools used in development including IDE, frameworks, and software quality assurance tools.
● Discussion of related software quality assurance theories and practices related to the project development
● Critical review of the software quality assurance
tools and techniques
used in the development and real practice experiences in the overall software development lifecycle.
● Discussion on future work if the project goes beyond the level defined in the coursework specification.
The Report should:
● Follow a logical Structure (Abstract, Preface, Main body, Conclusions, References )
● All sources should be acknowledged and fully referenced, including URLs etc. where appropriate
● Any quotations (from other sources) should be clearly marked as such, and referenced
● Be of publishable quality
Report presentation guideline and template are on
CANVAS
in
“Unit 1 - Introduction to Software Quality”
(I)
Marking scheme: Individual Report
Student Name: K No.: Marker:
Project Summary
( /10)
**
|
VG
|
G
|
F
|
P
|
VP
|
Overview of project aims and final outcomes
|
|
|
|
|
|
Summary of software engineering tools
|
|
|
|
|
|
Summary of software quality assurance work involved
|
|
|
|
|
|
Critical Review on SQ Theories and techniques
( /10)
**
|
VG
|
G
|
F
|
P
|
VP
|
Related software quality theories and critical review
|
|
|
|
|
|
Related software quality techniques and critical review
|
|
|
|
|
|
Reflections on SQA practices
( /10)
**
|
VG
|
G
|
F
|
P
|
VP
|
Reflections on chosen SQA tools
|
|
|
|
|
|
Reflections on SQA practices/techniques
|
|
|
|
|
|
Discussions on future work
|
|
|
|
|
|
Presentation
( /10)
**
|
VG
|
G
|
F
|
P
|
VP
|
Overall structure and format
|
|
|
|
|
|
Presentation
|
|
|
|
|
|
Referencing and citation
|
|
|
|
|
|