SUBMISSION OF THE PROJECT SOFTWARE REQUIREMENTS SP

Order this Assignment Now: $109

SUBMISSION OF THE PROJECT SOFTWARE REQUIREMENTS SPECIFICATION

The primary theme of the paper is SUBMISSION OF THE PROJECT SOFTWARE REQUIREMENTS SPECIFICATION in which you are required to emphasize its aspects in detail. The cost of the paper starts from $109 and it has been purchased and rated 4.9 points on the scale of 5 points by the students. To gain deeper insights into the paper and achieve fresh information, kindly contact our support.

Group Assignment 1:

Submission of the project Software Requirements Specification (SRS) Document and Access prototype.

Submission Due:

Week 7, online using the moodle system

Total Marks:

450 marks, for 10% total assessment

• SRS document: 160 marks
• Access Database: 140 marks
• XML Files: 100 marks
• Critical Analysis Section (evaluation and proposed solution): 50 marks

 

Purpose of the assessment:

The purpose of this assignment is to produce and submit a consolidated first version of the SRS document and the Access prototype for your project.

Projects:

1. Online Car Sales System -
2. Online Book Store –
3. Online Shopping -
4. Online Real Estate Business
5. Online Tour Booking System -
6. Online Dress Store -

 

 

 

Description: You have to submit:

1. The SRS document:
2. a) Should include your responses to all the headings in the template, including
3. b) Functional and non-functional specifications and appropriate diagrams, system goals
4. c) And objectives, target audience, system constraints, security planning, programming
5. d) Technology possibilities, technical constraints.
6. e) The document should follow the template provided.
7. f) The document should include all the required diagrams.
8. g) The report should be well written, properly formatted, with correct grammar, and no spelling mistakes.
9. i) The report presentation should be suitable for an external client.
10. j) The length is likely to be between eight and ten pages.

 

2. The Access prototype should include:
3. a) All the tables and attributes properly documented
4. b) The corresponding reading and writing forms for the tables.
5. c) The prototype will have a splash page at the start.
6. d) Enough functionality to see the prototype working.

 

3. XML Files: Express all the project entities using XML.
4. An up to date copy of the Project Activity Journal where you show the weekly working of the group.
5. Compare your SRS document with a provided good quality SRS documents (you can find them in your assignment folder, and select ANY one out of them for this purpose), and critically analyse you document’s strengths and weaknesses.

References and appendices

• Reference sources must be cited in the appropriate section of the document.
• All cited references in IEEE style
• List all the appendices

 

Marking guidelines:

Marks are allocated as follows:

 

SRS	Description of the section	Marks
Introduction	Outline of the project	10
General Description	Description of the project	10
Specific requirements	Functional and non-functional specifications, etc, as indicated in the template	50
Analysis models	Diagrams, figures, etc, as in the template	50
Appendices, references		10
Presentation	Appearance, grammar, clarity	30
Total		160

 

 

Access DB	Description of the section	Marks
Splash page	DB opening form	10
Data structure	DB data and metadata for the project, keys, etc	40
Functionality	Functions implemented	40
Forms	All the forms in the project	40
General navigation and appearance	Appearance, clarity	10
Total		140

 

XML	Description of the section	Marks
XML Schema	An XML Schema describes the structure of an XML document	30
Well Formed XML Documents	An XML document with correct syntax is called "Well Formed".	40
General appearance	Appearance, clarity	30
Total		100

 

Critical Analysis Section	Description of the section	Marks
Evaluation	Evaluate different types of alternatives for your selected project	25
Solution	Propose a better solution	25
Total		50

 

Extensions:

Requests for an extension will not normally be granted. A request, accompanied by supporting documentation, must be received in writing before 3 working days from the due date. Special consideration form is available on level 8 reception.

An extension will be granted only for the extent of the period covered in the accompanying certificates. That is, if granted, a one-day illness will result in a one-day extension.

Penalties may apply for late submissions without an approved extension.

 

Penalties:

Academic misconduct such as cheating and plagiarism will incur penalties ranging from a zero result to program exclusion.