Module 04 Lab - Basic User Interface Design
untitled folder/mmalik_Module 01 Course Project - Architect - Project Planning_10072017.doc
PAGE
1
Module 01 Course Project - Architect - Project Planning
Module 01 Course Project - Architect - Project Planning
Mohammad Malik
Rasmussen College
Author Note
This paper is being submitted on October 7, 2017, for Mohammad Malik CDA3315C Section 01 Fundamentals of Enterprise Architecture - Online Plus - 2017 Fall Quarter Term 1
Project Planning
· Scope: #INISOPE the scope of this project will basically be improvement of rate and quality of production. We seek to achieve precise command of production done digitally just by keying in what size ratios are required. This seeks to convert the company into a technocratic one.
· Resource Allocation: This project will need installation of a new production system that contains already programmed digital system. This technology will cost the company $55,000. There will be need for an installation team and a team that will be at the firm before, during and after implementation of the project to ensure everything is on course. Labour cost is as follows:
· Architecture - $150/hr for 5 hours a day
· Developer - $100/hr for 5 hours a day
· Other ‘outside’ employees (10) - $1,750 per week
· Automatic Generator - $ 8,000
· Timeline: As soon as this project commences, it will take exactly six months to completely run as planned:
· Procurement and Verification + Installation 2 Months
· Transfer of production from manual to digital 2 Months
· Follow up and meeting production thrust 2 Months
· Definition of Deliverables: At the end of the sixth month, the company should be able to produce its products digitally at the new rate (3 times more) with size specification as demanded.
· Task Assignments: Five of the outside employees will be taking part in first phase of the project, that is, Procurement and installation. The other five will take part in the second and final phase transfer of production and follow up duties.
· Quality Control: The quality control unit will entirely be conducted by the Architecture and the Developer with close supervision of the performance of the system until the sixth month after implementation. The commencing of this project is entirely in the hands of the company now. We would also like to have a time scale for the procurement calendar to help us in planning and budgeting for the project.
__MACOSX/untitled folder/._mmalik_Module 01 Course Project - Architect - Project Planning_10072017.doc
untitled folder/mmalik_Module 01 Course Project - Developer - Gather Functional Requirements_10072017.doc
1
Module 01 Course Project - Developer - Gather Functional Requirements
PAGE
2
Module 01 Course Project - Developer - Gather Functional Requirements
Module 01 Course Project - Developer - Gather Functional Requirements
Mohammad Malik
Rasmussen College
Author Note
This paper is being submitted on October 7, 2017, for Mohammad Malik CDA3315C Section 01 Fundamentals of Enterprise Architecture - Online Plus - 2017 Fall Quarter Term 1
Key Operational Requirements
#INISOPE following the need of improvements in performance and the incorporation of technology into your company, we have been able to figure out the fundamental changes in functions. We have been able to incorporate various attributes including speed and quality of production just as put by you as priority. This newly improved functionality seeks to improve your production rate three times the current rate of production. This is in line with the growing demand of your product, which will fill in the gap of demand and supply. Our priority here is meeting the customer needs of producing something light enough, water proof and easy to carry around.
To be able to meet some of these requirements, the system will be set to producing specific sizes of the product at different times of the working hours. The production rates in these hours will vary though since we have note that certain sizes may be on demand more than others. So, the system is fitted by digital control section that instructs it what sizes-ratio production should be produced depending on the variation of the demand. This will help in reducing the amount of raincoats that are warehoused longer than expected and thus reduces cost of production by 30%.
This project is highly depended on electrical power system. This means that your company will need a back-up plan in case of blackout. We would like to suggest that you procure an automatic pick-up generator that keeps the system running non-stop during working hours. We would also like to inform you that this project would cut down your employee capacity by over 50%. Since this project is picking up completely after the sixth of implementation, we advice that you keep the current capacity for emergency cases. Besides, since you are planning to grow into a larger scale of production, you can start planning a new branch that will accommodate the already specialized employees after the sixth month.
__MACOSX/untitled folder/._mmalik_Module 01 Course Project - Developer - Gather Functional Requirements_10072017.doc
untitled folder/mmalik_Module 02 Course Project - Architect - Setting a Baseline_10152017.docx
1
Module 02 Course Project - Architect - Setting a Baseline
2
Module 02 Course Project - Architect - Setting a Baseline
Module 02 Course Project - Architect - Setting a Baseline
Mohammad Malik
Rasmussen College
Author Note
This paper is being submitted on October 15, 2017, for Mohammad Malik CDA3315C Section 01 Fundamentals of Enterprise Architecture - Online Plus - 2017 Fall Quarter Term 1
AS-IS AND TO-BE ANALYSIS
Process Improvement with As-Is and To-Be Analysis
One effective technique for transforming vision into results is to develop and populate an As-Is and To-Be BPMN diagrams. The As-Is diagram describes the present state of the organization's process, culture, and capabilities. The To-Be diagram describes the future state; in other words, how the organization's process, culture, and capabilities will appear in the future.
The main purpose of an as-is diagram needs to work out where improvements are needed and what is the starting point for change. On the other hand, to-be diagram requires business analysts to be creative in solving problems and designing processes to achieve business outcomes, often only based on imperfect information about what the organization actually wishes to accomplish.
Software tool we'll be using
Visual Paradigm provides a robust means to capture the current business process, design enhancement and identify the enhancement between the current and enhanced processes.
Capture the Current Process in As-is Process
The example that we are going to demonstrate is about an online shop that sells goods. The process begins with the sales representative receives a purchase order from a customer and proceeds to check the stock level. If there is enough stock on hand to meet with the order, the sales representative will pack them. The process ends with shipping them along with an invoice. In case of insufficient stock, the sales representative will suggest the customer to amend the purchase order.
Once the business process of your existing operation has been created, you can then derive the to-be process model by considering and projecting the necessary improvements or changes needed to be made based on the existing to-be process. Walk through the steps in this tutorial to see how things work.
1. Download Online-Shopping.vpp. You can also find this file at the bottom of this tutorial.
2. Open the downloaded .vpp file in Visual Paradigm. To open a project, select Project > Open from the application toolbar.
3. Open the Project Browser by selecting View > Project Browser from the application toolbar.
4. Open the Model Structure tab.
5. Right click on project root node in the tree on the left hand side and select Model > As-is Process from the popup menu.
6. Right click As-is Process and select Sub Diagrams > Existing Diagrams... from the popup menu.
7. In the Add Sub Diagram window, select the only business process diagram and click OK.
Now your existing process is being contained under the as-is Process model.
Re-design to Enhance the Current Process in To-be Process
Let's just say that our business has grown so much that we now have a warehouse to keep our stocks. So we are looking for ways to improve our current (as-is) process to better allocate the new resources. Furthermore, we will show an example of modeling the enhancement below in a to-be process diagram.
1. Open the business process diagram by double clicking on its thumbnail in Project Browser
2. Create a to-be process diagram from the current process diagram. Right click on any white space in the background of the as-is process diagram and select Utilities > Create To-be Process.
You'll see that a new diagram is created containing the to-be process.
Note: Initially, all model elements are selected in the new diagram. To deselect, click any white space in the background.
3. Add a lane to
Online Shop. Name it
Warehouse. In the
Sales Representative lane, select
Pack Goods, Ship Goods and
Order completed and drag them to the
Warehouse lane. Your diagram should look like the one below.
4. We are going to insert a task between
Sufficient Stock? and
Pack Goods. Place your mouse pointer over the
Yes flow coming from
Sufficient Stock? and then click on the resource button Split with Shape.
5. Select Task from the popup menu.
6. Name the new task
Request Pack Goods. The completed to-be process diagram should look like something like this.
Compare Changes in As-is Process and To-be Process
To compare the differences between two diagrams visually, we can make use of a function called Visual Diff.
1. Select Modeling > Visual Diff... from the appliaction toolbar.
2. In the Visual Diff window opened, select Transitor for Strategy. For Compare, select Model Element to be the level to compare our diagrams.
3. Check the checkboxes next to Use Working Project. Select
As-is Process on the left. Select
To-be Processon the right. The comparison will be triggered automatically.
For example, from the list below the diagrams, we know that changes were made to
Pack Goods as it says
Pack Goods (Modified). If you click on the row, you will see the corresponding changes in purple in the diagrams.
New tasks will be noted as well. Remember (in the enhancement) we have added a new task for the sales representative to request for the warehouse to pack goods? That is also "spotted" in our list.
image2.png
image3.png
image4.png
image5.png
image6.png
image7.png
image8.png
image9.png
image10.png
image11.png
image12.png
image13.png
image14.png
image15.png
image16.png
image1.png
__MACOSX/untitled folder/._mmalik_Module 02 Course Project - Architect - Setting a Baseline_10152017.docx
untitled folder/mmalik_Module 02 Course Project - Developer - Set Up Database_10152017.docx
1
Module 02 Course Project - Developer - Set Up Database
Module 02 Course Project - Developer - Set Up Database
Mohammad Malik
Author Note
This paper is being submitted on October 15, 2017, for Mohammad Malik CDA3315C Section 01 Fundamentals of Enterprise Architecture - Online Plus - 2017 Fall Quarter Term 1
Entity Relationship Diagram
The entity relation diagram shows the relation of data obtained from Inisope, Inc. project. To get an overview of database structure, I connected to the Oracle data source, which automatically generated the Entity Relationship Diagram based on the HR directory data. This model highlights a better understanding of the database to be installed in the information systems of the company. There are six entities as depicted on the ER diagram mainly: Countries, region, location, departments, jobs, job description, and employees. The ER diagram is vital to Inisope, Inc. in debugging and designing its business information systems for its disposable dog raincoats. It is significant in the planning stage of the project. The entities are interconnected to form a business system that depicts how information and business are performed from one stage to the next. During the developmental stage of the project, there should be a smooth flow of information.
The ER diagram best visualizes the database tables. Lines representing the primary and foreign key entities and attributes connect them. These lines only act as a key between the two fields. Countries as an entity are connected to the region to show that the organization moves its products based on geographical size. These countries are USA, China, Taiwan, Russia, Mexico, European countries and Canada. An entity like Employees has attributes like names, salary, phone number, date of hire etc. This best describes the employees working in the company. When this data is entered into a computer database system, every employee can be identified based on country, region, department, job, job description and location. This model best captures the data needs of the end user for verification purposes. Once the database architecture has been developed, the company can conduct its research focusing on the structured data. It will be beneficial in uncovering information easily and therefore improve and streamline business processes.
image1.png
__MACOSX/untitled folder/._mmalik_Module 02 Course Project - Developer - Set Up Database_10152017.docx
untitled folder/mmalik_Module 03 Course Project - Architect - Setting Our Target_10222017.docx
1
Module 03 Course Project - Architect - Setting Our Target
Module 03 Course Project - Architect - Setting Our Target
Mohammad Malik
Rasmussen College
Author Note
This paper is being submitted on October 22, 2017, for Mohammad Malik CDA3315C Section 01 Fundamentals of Enterprise Architecture - Online Plus - 2017 Fall Quarter Term 1
To-be Model of the new Isonope company directory
Model views for the end users
Model view for the business managers
The developed new system will not only save money but also improve efficiency and increase profitability value to the business. This means that system will add great value to the business. The end users and business managers’ views stipulate the starting points and destination of the business. The models above look at the problems in an architectural framework then divide the problems to come up with a coherent solution. When designing the models the following were considered: the business process, the business functions, the products, the business units and business objects.
The viewpoints in the models define the abstractions that each stakeholder addresses the concerns. The viewpoints may be used to relate to two or more aspects. Furthermore, the viewpoints in the models above clearly represent the schemes or layouts of the organization. This assists in applying different knowledge the addresses the problems in the company. The models combine the idea of actors, agent or role in the development process with the notion that the views of the stakeholders or actors will be maintained. The viewpoint normally contains the behavior, identity, and state of the company.
The viewpoints described in the above models should not be ignored as they rely on each other in achieving the desired final goal. However, a viewpoint is just one part of the system architecture in an organization. In the above two models, the views show all the information about architecture areas. A view is defined using a viewpoint which in turn describes the models, concepts, visualization and analysis techniques used in the views. The stake holders involved in the model's viewpoints include the end user, upper-level management, the architect, operation manager, project manager, and finally the developer