Assessment item 2 Requirements Gathering Value: 25% Due Date: 25-Aug-2019 Return Date: 13-Sep-2019 Submission method options: Alternative submission method Task Further background Refer to the...

1 answer below »


Assessment item 2



Requirements Gathering



Value:25%



Due Date:25-Aug-2019



Return Date:13-Sep-2019



Submission method options:Alternative submission method



Task



Further background



Refer to the Project Vision Document submitted in Assessment Item 1 regarding Auto-Parts Warehouse Management System. In this assignment, you are required to prepare a report that describes the detailed architecture and design of the proposed system.




Complete the Following



Please refer to the marking guide when preparing your response to see what criteria and standards will be used to assess your work and your progress.


Amongst the information sought are answers to the following questions:


1. Identify and briefly describe the functional and non-functional requirements for the proposed system. (2 pages, times new roman, size 12)


2. Identify use cases and draw use case diagrams for the proposed system that show major use cases and actors.


3. Draw domain model class diagrams for the proposed system. Be as specific and accurate as possible, if needed information is not given, make realistic assumptions.


4. Develop an event-partitioned system model encompassing all the use cases you identified in question 2. Assume that the classes and associations in question 3 correspond to entities and relationships from similar entity relationship diagrams.



Rationale


This assessment task will assess the following learning outcome/s:



  • be able to compare and contrast the different methodologies of systems analysis and evaluate their appropriateness for different and complex situations.

  • be able to distinguish between requirement gathering techniques and combine these appropriately to apply to a real scenario.

  • be able to formulate and justify system requirement models based on evaluation of given situations.

  • be able to assemble the components of a requirements model using the tools and techniques of object oriented or structured systems modelling.



Marking criteria and standards
































































Criteria




High Distinction (HD)




Distinction (DI)




Credit (CR)




Pass (PS)




Fail (FL)



1. Identify and briefly describe the functional and non-functional requirements.


4 Marks



Functional requirements: all nine major business rules are identified and briefly described;


Non-functional requirements: seven possible system characteristics are identified and briefly described.



Functional requirements: seven major business rules are identified and briefly described;


Non-functional requirements: five possible system characteristics are identified and briefly described.



Functional requirements: five major business rules are identified and briefly described;


Non-functional requirements: four possible system characteristics are identified and briefly described.



Functional requirements: three major business rules are identified and briefly described;


Non-functional requirements: three possible system characteristics are identified and briefly described.



Identified functional and non-functional requirements are wrong and no or little description.



2. Identify use cases and draw use case diagrams


5 Marks



Major use cases are identified with accurate use case diagrams for the proposed system that show major use cases and actors.



Major use cases are identified with mostly accurate use case diagrams for proposed system that show major use cases and actors.



Some of the major use cases are identified with mostly accurate use case diagrams for proposed system that show some use cases and actors.



Few use cases are identified with use case diagrams for few proposed system that show few use cases and actors.



Use cases and use case diagrams are wrong.



3. Draw domain model class diagrams.


8 Marks



Domain model class diagrams are accurate for the proposed system; identified all possible domain classes and some attributes, showing logical relationships among all domain classes.



Domain model class diagram are mainly accurate for the proposed system; identified all possible domain classes and some attributes, showing logical relationships among all domain classes. Some omissions.



Domain model class diagrams are accurate for the proposed system; however, domain classes and their attributes are not always accurate, logical relationships have some errors among domain classes.



Domain model class diagrams are not always accurate for the proposed system; domain classes and their attributes are not always accurate, logical relationships have some errors among domain classes.



Domain model class diagrams have major omissions.



4. Develop an event-partitioned system model encompassing all the use cases you identified in question 2.


5 Marks



Event-partitioned system model is accurate for the proposed system; identified all possible processes, agents, and data entities, showing logical relationships among all items.



Event-partitioned system model is mostly accurate for the proposed system; identified most of processes, agents, and data entities, showing logical relationships among most of the items.



Event-partitioned system model is mostly accurate for the proposed system; identified most of the possible processes, agents, and data entities, showing logical relationships among all items. Some omissions.



Event-partitioned system models is not always accurate for the proposed system; identified only some processes, agents, and data entities, showing logical relationships among some items.



Event-partitioned system model is wrong.



Presentation and clarity (accuracy, spelling, grammar, punctuation, figures)


2 Marks



Fluent writing style appropriate to the assignment with accurate grammar and spelling, and high-quality figures drawn using some tools and figures have some captions.



Mostly fluent writing style appropriate to assignment with accurate grammar and spelling, and good-quality figures drawn using some tools and figures have some captions.



Mostly fluent writing style appropriate to the assignment with mostly accurate grammar and spelling. Minor omissions only. Some-quality figures drawn using some tools and figures have some captions.



Writing style not always fluent or well organised and grammar and spelling contain errors. Poor-quality figures drawn using some tools and figures have some captions.



Writing style not fluent or well-organised, and many grammatical and spelling mistakes. Very bad quality figures, copied from others work, no captions.



Referencing and Citation
1 Marks



Referencing is mainly accurate and according to the APA standard. All references are cited in the text.



Referencing is mainly accurate and according to the APA standard. Most of the references are cited in the text.



Some attempt at referencing and according to the APA standard. Few references are cited in the text.



Attempt at referencing but not exactly according to APA standard and only few references are cited in the text.



Referencing is absent/ unsystematic.





Presentation


Only task 1 about to identify and briefly describe the functional and non-functional requirements should be 2 pages long, font times new roman, size 12. For other tasks in this assignment, please follow marking criteria and standard. All figures must have suitable caption and cited (if required) within text using APA standard.


Answered Same DayAug 30, 2021

Answer To: Assessment item 2 Requirements Gathering Value: 25% Due Date: 25-Aug-2019 Return Date: 13-Sep-2019...

Amit answered on Sep 01 2021
147 Votes
Title of the assignment: Assignment - 2
Student’s name:
Student ID:
Professor’s name:
Course title: ITC 548 (Report on architecture and design)
Date: 9/1/2019
Table of Contents
1.    Introduction    3
2.    Functional and non-functional requirements    3
3.    Use cases and their diagrams    5
4.    Domain model class diagr
am    10
5.    Event partitioned system model    11
6.    References:    12
1. Introduction
The implementation of poor management system for Auto-parts ware house can create issues in warehouse management. The record management for auto parts will provide sufficient directions to this company. The auto parts details, their stock, transportation and many other things can easily be managed with implementation of this management system. The record management will lead to effective processing of orders and all emergency states can be managed easily. The generation of different required reports will also becomes easy and operational success for auto parts warehouse can be archived. The process optimization, effective labor uses, improved moral of employees, reduced operational costing; effective ERP implementation and better relationships with all customers can be developed. So, this proposed system will bring huge benefits to this auto parts ware house.
2. Functional and non-functional requirements
The implementation of this warehouse system will be based on certain requirements and these requirements can be based on its functionalities or any other non functional requirements [Dennis et al, 2015]. The requirement analysis is mainly conducted to find all possible requirements and make assure that all these requirements are properly implemented while deployment of the required system. The identified functional requirements for this management system of auto parts warehouse are listed below:
· Implementation of dynamic procedures: The current management system of this Auto parts warehouse is not making use of ant dynamic producers. The static procedure for making inventories is used by this ware house. The implementation of new management system must bring dynamic procedure implementation for maintaining different inventories of auto part item movement and their storage.
· Order management with inventory control: The current system is not properly implementing the order management of auto parts from different clients. The proper control on inventory system will bring the required order management for this ware house.
· Effective processing of orders: Different clients make different requests for auto parts and effective processing of these orders must be done by this newly proposed system.
· Processing of order pickup: The ware house has to provide facility to pick and drop different placed orders on client side. The new system must have to manage the queue for processing this pickup and drops.
· Load management of placed orders: The increased load of placed order must be managed by the newly proposed system for auto parts warehouse. The system must not slow down in performance while processing the increased load of incoming orders.
· Alert generation: The placed orders will have certain...
SOLUTION.PDF

Answer To This Question Is Available To Download

Related Questions & Answers

More Questions »

Submit New Assignment

Copy and Paste Your Assignment Here