GET READYMADE HS2011 SYSTEMS ANALYSIS AND DESIGN ASSIGNMENT SOLUTIONS - 100% PLAGIARISM FREE WORK DOCUMENT AT NOMINAL CHARGES!
HS2011 Systems Analysis and Design Assignment - Holmes Institute, Australia
The Company - Ceylon Textile Suppliers (CTS),
Project requirement - As a first step of the proposal, the Holmes consultants have prepared an initial review report that includes current processes related to sales orders, stock control and advertising campaign. Your task is to provide a system vison and requirement models for each subsystem and other necessary information to represent the current level scope, as indicated by the consultant's report.
Answer - System Analysis and Design
Activity diagrams
Activity Diagram
The operation diagram to describe complex system elements is another important behavioral diagram in the UML diagram. The activity diagram is basically a complicated flow chart version modeling the flow from one operation to another. Activity Diagrams describe how operations can be structured to provide a function at different levels of detail. Generally, some activities need to execute an activity, particularly where the operation is planned to achieve a variety of things that involve planning, or how events in a single-use case relate to each other, specifically where processes that overlap and need decision making. It is also important to design how a series of use cases organize client workflows. The activity diagram represents the business process for the organization. This activity diagram represents the business process of stock controls for the business process.
Activity Diagram of Stock Control Department
The following activity diagram represents the business process of stock control department.
Activity Diagram for Sales Orders Department
The following activity diagram represents the business process of sales orders department.
MOST RELIABLE AND TRUSTWORTHY HS2011 SYSTEMS ANALYSIS AND DESIGN ASSIGNMENT HELP & HOMEWORK WRITING SERVICES AT YOUR DOORSTEPS!
Event Tables
An event tables are created with the help of use case diagrams. The event tables represent the events which are created by the different department.
|
Event
|
Trigger
|
Source
|
Use Case
|
Response
|
Destination
|
|
Maintaining Stock Level
|
Update the status of the stock
|
Stock Manager
|
Records of stock are maintained
|
Place order to maintain the stock
|
Sales Team Leader
|
|
Raise sales order
|
Passed sales order
|
Travelling sales team
|
Record of orders are maintained
|
Print multi part sales order
|
Stock Department
|
|
Order filled by stock
|
Provide dispatch note
|
Source Manager
|
Release of dispatch note
|
Customer
|
Sales Department
|
|
Dispatch note
|
Passed to stock room
|
Sales Team
|
Release of dispatch note
|
Picking of order
|
Stock Department
|
|
Establish new Product
|
New Product has been developed
|
Product Manager
|
Record of new product will maintained
|
Product has been developed
|
Board of directors
|
|
Delivery Report
|
Received order
|
Sales Manager
|
Delivery report has been sent
|
Receiving of delivery report
|
Stock Manager
|
User Stories and Acceptance Criteria
These can be seen as a clear description that determines the feature of the business model, user flow or solution. Test-instance acceptance requirements act as a catalyst and should be testable. Acceptance criteria have a comprehensive requirement range that helps the team comprehend the value and enables the group to diagonally slice the user story.
A user story's acceptance requirement is an element that should have. An acceptance criterion is a document specifying the fulfillment of all user story criteria and when a user story functions.
As soon as the developer remark the user story as 'done'. There must be fulfillment of criteria that ensure the user story and it work as planned and tested.
Generally deciding what the eligibility criteria should be for which user story is the responsibility of the product holder. The eligibility criteria make the functionality very versatile when developing an ideal user narrative, helping the item's proprietor uncover any missing point and confirm the thesis. If any theory is incorrect, much sooner it will help identify. Acceptance Criteria should include following:
- Negative functionality scenarios.
- The impact on other features of a user story.
- Cases of functional or non-functional use
- Functional or non-functional applications
- Concerns about performance and instructions.
- What scheme / function will you do?
- The function system does nothing, it is not intended to do anything
- End-to-end user flow
SAVE DISTINCTION MARKS IN EACH HS2011 SYSTEMS ANALYSIS AND DESIGN ASSIGNMENT WHICH IS WRITTEN BY OUR PROFESSIONAL WRITER!
Data Flow Diagram
Context Diagram
The context diagram is used to evaluate the scope and weaknesses of the modeling system: what is within and outside the modeling scheme, and what is the relation between the system and these specific entities. A context diagram is used to define and describe the programming system's weaknesses, also called an information flow diagram at level 0. This describes flows of information between the system and external entities. The whole system of software is shown as method.
Level One Data Flow Diagram
A level 1 DFD notes each of the popular post-processes forming the full scheme together. We can believe of a stage 1 DFD as the context diagram's "exploded perspective."
Zero Data Flow Diagram
Data dictionaries
|
Table Name
|
Field Name
|
DataType
|
Length
|
Description
|
|
Customer Table
|
Customer_ID
|
Integer
|
10
|
PK of the customer table
|
|
Customer_Name
|
Varchar
|
25
|
Name of the customer
|
|
Address
|
Varchar
|
50
|
Customer address
|
|
Payment
|
Varchar
|
25
|
Payment of the product
|
|
Supplier_ID
|
Integer
|
10
|
FK, Define the supplier id
|
HIRE PROFESSIONAL WRITER FROM EXPERTSMINDS.COM AND GET BEST QUALITY HS2011 SYSTEMS ANALYSIS AND DESIGN ASSIGNMENT HELP AND HOMEWORK WRITING SERVICES!
|
Table Name
|
Field Name
|
DataType
|
Length
|
Description
|
|
Supplier table
|
Supplier_ID
|
Integer
|
10
|
PK of the supplier table
|
|
Supplier_Name
|
Integer
|
10
|
Name of the supplier
|
|
Phone
|
Integer
|
10
|
Phone no of the supplier
|
|
Payment
|
Varchar
|
25
|
Payment of the product
|
|
Product_ID
|
Integer
|
10
|
Define the Product id
|
|
Stock_control
|
Varchar
|
25
|
Stock control manage
|
|
Production
|
Varchar
|
25
|
Stock raw material mange
|
Process Description
Data dictionary level 1 diagram
|
Field Name
|
DataType
|
Field Size
|
Description
|
|
Customer
|
Varchar
|
225
|
Contains the record of the customer
|
|
Product Management
|
Varchar
|
225
|
Records of the products
|
|
Online Purchase
|
Varchar
|
225
|
Record of the customer or supplier
|
|
Admin
|
Varchar
|
225
|
Admin controls the whole system
|
|
Sales Management
|
Varchar
|
225
|
Maintain the record of sales team members
|
|
Account Management
|
Varchar
|
225
|
Maintain the record of accounts
|
WE HELP STUDENTS TO IMPROVE THEIR GRADES! AVAIL TOP QUALITY HS2011 SYSTEMS ANALYSIS AND DESIGN ASSIGNMENT HELP AND HOMEWORK WRITING SERVICES AT CHEAPER RATE!
|
Field Name
|
DataType
|
Field Size
|
Description
|
|
Customer
|
Varchar
|
225
|
Contains the record of the customer
|
|
Stock Manager
|
Varchar
|
225
|
Contains the record of the stock level
|
|
Supplier
|
Varchar
|
225
|
Contains the record of the suppliers
|
|
Accountant
|
Varchar
|
225
|
Contains the record of the accounts
|
|
Stakeholder
|
Varchar
|
225
|
Contains the record of the stakeholders
|
Use cases diagram
Sales order use case diagram
Stock use cases
Product use cases
NEVER MISS YOUR CHANCE TO EXCEL IN HS2011 SYSTEMS ANALYSIS AND DESIGN ASSIGNMENT! AVAIL AFFORDABLE AND RELIABLE HS2011 SYSTEMS ANALYSIS AND DESIGN ASSIGNMENTS HELP SERVICES OF EXPERTSMINDS.COM!
Use cases descriptions
Description -
|
Use Case Id:
|
1
|
|
Use Case Name:
|
Product
|
|
Created By:
|
Department
|
Last Updated By:
|
Department
|
|
Date Created:
|
08/10/2019
|
Date Last Updated:
|
08/10/2019
|
|
Actors:
|
Customer, sales manager, product manager Board of directors
|
|
Description:
|
Product Details
|
|
Trigger:
|
Customer view product and purchase product
|
|
Preconditions:
|
Product manager and BOD manage the order
|
|
Post conditions:
|
Product accepted or rejected
|
|
Normal Flow:
|
Manage the order and supplier product
|
|
Alternative Flow:
|
Satisfaction of customer
|
|
Exceptions:
|
Product will be purchased
|
|
Use Case Id:
|
2
|
|
Use Case Name:
|
Sales order
|
|
Created By:
|
Department
|
Last Updated By:
|
Department
|
|
Date Created:
|
08/10/2019
|
Date Last Updated:
|
08/10/2019
|
|
Actors:
|
Customer, supplier, Board of directors
|
|
Description:
|
Supplier communicate with clients
|
|
Trigger:
|
Salesperson provide quotation to the client
|
|
Preconditions:
|
Supplier and BOD manage the order
|
|
Post conditions:
|
Either quotation accepted or rejected
|
|
Normal Flow:
|
Smooth Running
|
|
Alternative Flow:
|
Satisfaction of customer
|
|
Exceptions:
|
Product will be purchased
|
NO PLAGIARISM POLICY - ORDER NEW HS2011 SYSTEMS ANALYSIS AND DESIGN ASSIGNMENT & GET WELL WRITTEN SOLUTIONS DOCUMENTS WITH FREE TURNTIN REPORT!
Listed below some of the major courses cover under our Holmes Institute, Australia Assignment Help Service:-
- HS2031 Human-Computer Interaction Assignment Help
- HS2021 Database Design and Use Assignment Help
- HS3021 Strategic Information Systems Management Assignment Help
- HS3011 Information Security Assignment Help
- HS3041 Business Intelligence and Knowledge Management Assignment Help
- HS1021 Web Design Assignment Help
- HS1011 Data Communications and Networks Assignment Help
- HS2061 Information Systems Project Management Assignment Help
- HS2041 Enterprise Systems Assignment Help
- HS3031 Sustainability & IT Practice Assignment Help
- HS2021 Database Design and Use Assignment Help