Reference no: EM13841997
Program Architecture
This section is best completed with either a Physical DFD (SAD) or a Class Diagram (OOAD). The purpose is to define the physical architecture of the programs as they interface with each other. The diagram should include every module that will be part of the application.
Component Interfaces
Provide a screen navigation diagram and an Event chart/list. If it needs to be described by a narrative then you should provide that as well.
PURPOSE of the project is Williams Specialty Company (WSC) requested a business automation application in which will allow for the WSC employees be able to automate customer service, inventory, and quality control. This project will deliver an application that will keep track of the processes with a database. The purpose of the application is to accelerate and improve the management of the customer orders and processes. The features that will be included are:
• Create, modify, and store customer orders
• Access to the database (only by the manager and sales person)
• Create memos and e-mails within the employees and save them within the database
• Validate customer orders
• Mark order as "complete"
1. 1. Scope
This section will define the scope of the project by defining and describing the System, the major functions of the application, and the database.
1.1. 1.1. System Description
2. Williams Specialty Company (WSC) requested a business automation application in which will allow for the WSC employees be able to automate customer service, inventory, and quality control. This project will deliver an application that will keep track of the processes with a database. The purpose of the application is to accelerate and improve the management of the customer orders and processes. The features that will be included are:
3. • Create, modify, and store customer orders
4. • Access to the database (only by the manager and sales person)
5. • Create memos and e-mails within the employees and save them within the database
6. • Validate customer orders
7. • Mark order as "complete"
7.1. Major Software Functions
The business application being created will allow for Order capture by the Williams Staff. Assign that order to a specific employee. Store this Information in an Oracle or Microsoft SQL Database(To be discussed). Allow access to this database to managers and sales people. As well as provide communication between the employee assigned to the order and the Sales team and management via Internal Electronic Communication( Email and Memo). As well as create a Customer satisfaction and follow up communication on Completion of the order(Via Email). Then Mark Inventory as Complete and help maintain Inventory Control and improve Order completion.
Diagram To Follow...
7.2. Database Description
The Project will utilize an Oracle or Microsoft SQL Database engine.
7.1. 1.4. Design Constraints and Limitations
The Design Constraints within this project will be Conforming the application to Run on Their Current Infrastructure. (Windows 7 OS and Windows 2012 Server).
The Second Design Constraint will be creating this application in such a way that it is easy to access(Low level of technical knowledge needed) as well as easy to maintain.