Project Overview For your course project, you will be working on a case study. The details are below. The Client Inisope, Inc. is the market leader in disposable dog rain coats. They come on a roll like baggies and use tabs (like diapers) to attach to the bottom of a dog's legs. They come in a variety of sizes. When you get back from the walk, you can simply throw it away with no smelly mess. The Project Inisope was founded by Austin Fichtner as a single person business run out of an apartment but has grown to over 2000 employees. However, their I.T. and internal processes have not kept pace with this growth and as a result are a patchwork of different systems and workflows. There are several opportunities for improvement but you'll need to talk to the client to find out just what they need. The Team Each team will consist of two members, the architect and the developer. The architect is the project lead and is responsible for project planning, budgeting, high-level design and direct contact with the client. The developer works with the architect on design details, converts functional requirements into a workable design and builds the system. As project lead you will be hiring a developer in Week 1. Your goal is to produce a pilot system for the client so they can decide whether to go to production. In addition to producing the desired functionality, you will need to estimate time and costs for a production system as well as hardware and software budgets. NOTE: The architect bills at $150/hr. and the developer bills at $100/hr. You need to track the time each spends on project work so you can present the client with an itemized invoice upon completion. Further Notes Your instructor will be taking on the role of the client. With that in mind, when you email them any messages that are for the client should have a subject line that starts with #INISOPE to distinguish them from course-related emails. In addition, a portion of each week's Live Classroom will take the form of a weekly client meeting. You will need to meet with your team at least once per week. This can be by phone, text messaging, video chat or whatever method works for you both as long as it takes place in real-time (i.e., not email). Due Date Your final project is due in Module 06. There will be individual assignments along the way. The module they are due is noted in the time line below. 1 Robert Jamerson Modeling Transformation Inisope, Inc., is a very marketable company that should be able to expand its business based on the technological trends for it to grow and be able to handle its client and the number of workers that are in the company. Maintaining the number of customers and workers in the system requires investing on developing a current system that will be in a position to meet the requirement of the user and customer. It should be also cost effective, reliable, easy to use and environmental friendly (Huang, Viti, & Tampère, 2016). To come up with a system that bri.

1. Project Overview
For your course project, you will be working on a case study.
The details are below.
The Client
Inisope, Inc. is the market leader in disposable dog rain coats.
They come on a roll like baggies and use tabs (like diapers) to
attach to the bottom of a dog's legs. They come in a variety of
sizes. When you get back from the walk, you can simply throw
it away with no smelly mess.
The Project
Inisope was founded by Austin Fichtner as a single person
business run out of an apartment but has grown to over 2000
employees. However, their I.T. and internal processes have not
kept pace with this growth and as a result are a patchwork of
different systems and workflows. There are several
opportunities for improvement but you'll need to talk to the
client to find out just what they need.
The Team
Each team will consist of two members, the architect and the
developer. The architect is the project lead and is responsible
for project planning, budgeting, high-level design and direct
contact with the client. The developer works with the architect
on design details, converts functional requirements into a
workable design and builds the system. As project lead you will
be hiring a developer in Week 1.
Your goal is to produce a pilot system for the client so they can
decide whether to go to production. In addition to producing the
desired functionality, you will need to estimate time and costs
for a production system as well as hardware and software
budgets.
NOTE: The architect bills at $150/hr. and the developer bills at
$100/hr. You need to track the time each spends on project work
so you can present the client with an itemized invoice upon
completion.

2. Further Notes
Your instructor will be taking on the role of the client. With
that in mind, when you email them any messages that are for the
client should have a subject line that starts with #INISOPE to
distinguish them from course-related emails. In addition, a
portion of each week's Live Classroom will take the form of a
weekly client meeting.
You will need to meet with your team at least once per week.
This can be by phone, text messaging, video chat or whatever
method works for you both as long as it takes place in real-time
(i.e., not email).
Due Date
Your final project is due in Module 06. There will be individual
assignments along the way. The module they are due is noted in
the time line below.
1
Robert Jamerson
Modeling Transformation
Inisope, Inc., is a very marketable company that should be able
to expand its business based on the technological trends for it to
grow and be able to handle its client and the number of workers
that are in the company. Maintaining the number of customers
and workers in the system requires investing on developing a
current system that will be in a position to meet the requirement
of the user and customer. It should be also cost effective,
reliable, easy to use and environmental friendly (Huang, Viti, &
Tampère, 2016).
To come up with a system that brings the employee’s directory
to production, adding features such as searching on multiple
fields, administrative page for updating records, exporting the
results to different format, selling their products and physical
expansion requires a total procedure which undergoes a system
design life cycle. This is standard procedures that is used to
develop a system from scratch to its working states.
System design life cycle consists of several tailored phases that

3. are used to manage a wide range of the activities to conduct
projects that happen within any operating system and every
other company applying the use of any management information
system as a tool to operate daily activities within the company
(Shirayama, Itoh, & Fukushima, 2017).
The company should first state the purpose, background, and the
basics of the system. By doing so, system designer can manage
to get a clear overview of what is required. In addition to
stating user requirement and customer needs, Inisope should be
in a position also give a status of the current system in place
before embarking or taking a step in developing the new system.
This will give a clear and precise picture on how the new
system will be expected to perform.
System development life cycle have seven phases that are
required to be followed in a step by step manner. These are;
· Project definition
· User needs or requirements
· System/data requirements definition
· Analysis and design
· System build/prototype/pilot
· Implementation and training
· Sustainment
All these processes of system development life cycle are not an
idea of common practice in performing daily routine and tasks
but in another way, is a critical to develop strategy to assist in
daily tasks that is needed by every companies. (Shirayama, Itoh,
& Fukushima, 2017).
PROJECT DEFINITIONS
It prompts the collection of information to determine if a
project will be worth the investments of either personnel or
financial support. The project proposal should identify the end
user, customer, purpose, and basic operating concept. It should
provide the preliminary investigation of different choices, risk
analysis to access the project if there is a return on investment.
The project details should be a position to show the expected
cost increases or decrease and the amount of profit that will be

4. gained.
USER REQUIREMENTS DEFINITION
It is based on the whole process that the end user conducts in
their daily routine. It should clearly describe what portion of
the end user activity should be computerized or enhanced and
expected working strength and features. Before developing a
user and requirements, there are tasks that should be followed
namely; defining operating strategies, interviewing and
objectives notifying.
SYSTEM/DATA REQUIREMENTS DEFITION
It is based on putting together user activities and requirements
in a way that will give permission a system to support multiple
and different user functions in the same way. It marks the
development of the key technical areas to use technology. The
purpose of data requirements is to establishment a sub-set to
incorporate existing system and technologies which is used by
the organization. This is a critical road map for any system
designed to process data. This explains how the system should
be built,what data should be processed and what technical or
support requirements may be required.
ANALYSIS AND DESIGN
It is a complex phase and critical step in accessing which design
based on system engineering and technology analysis that
satisfies the user requirement and system (Huang, Viti &
Tampère, 2016). The most important milestone in this phase is
the recommendation of what to do or buy to accomplish the user
and system requirements.
SYSTEM BUILD/PROTOTYPE/PILOT
It is where the execution of approved design and in some
occasions, may blend into the implementation phase. A proof-
of-concept validation is at times required prior to committing
financial supports for a huge scale fielding of a system. Without
the idea if it will work as intended by the user (Bellingham,

5. 2007). The concept of this phase is to validate the design before
fully committing yourself into the task.
IMPLEMENTATION AND TRAINING
This phase includes all necessary required activities to
purchase, receive, configure and install the new or revised
system. In the other hand on non-technical solutions,
implementation may be limited to new support activities
requiring a change in the business process. During this phase
training is conducted in accordance to the training plan which
would have been created in one or more of the previous phases.
A transition or cut-over plan requiring data conversion will also
be required to ensure a smooth transition to the new system
simultaneously (Huang, Viti, & Tampère, 2016). The
appropriate documentation such as manuals for operations and
maintenance are required. Testing also takes place in this phase
and validates the usability of the system or support activities
through reports such as test analysis, security evaluations, and
system accreditations. The key results of this phase are a
successful transition to the new system with uninterrupted
services.
SUSTAINABILITY
It is a dedicated effort to keep the system operating at an
optimum level by conducting maintenance and enhancement as
determined periodically. Changes in the needs, environment,
customer needs and end user needs or technology may prompt
business process improvement or reengineering initiatives to
validate or develop it in a new way. For any company to grow,
it should learn to embrace the technology by investing on
research and finding different methodologies. Understanding the
current system and the task allocated to every user is also a
crucial step to identifying the all picture on what is going on.
Having the picture all the organization and corporate companies
will be able to understand their operations and tasks that should

6. be implemented and put in place (Bellingham, 2007). Inisope
should follow the steps to expand the operation of their
company, manage clients and workers basing on the increase in
number of workers against the reliability of the current system.
By doing so, they will accomplish the requirements of the users
as well as clients.
References
Bellingham, J. G. (2007). New oceanographic uses of
autonomous underwater vehicles. Marine Technology Society.
Marine Technology Society Journal, 31(3), 34.
Huang, W., Viti, F., & Tampère, C. M. (2016). A dual control
approach for repeated anticipatory traffic control with
estimation of network flow sensitivity. Journal of Advanced
Transportation, 50(7), 1386-1412.
Shirayama, Y., Itoh, H., & Fukushima, T. (2017). Recent
Developments in Environmental Impact Assessment regarding
Mining of Deep-Sea Mineral Resources. In Deep-Sea Mining
(pp. 445-463). Springer International Publishing.