Final Projectx - Marc Grosz Wiki

snailyakSecurity

Nov 5, 2013 (3 years and 7 months ago)

101 views

Problem:

As the ASP industry has evolved from an infant
-
like beginning,
many vendors have developed a
disparate selection of web services
.
T
hese
proprietary web
services
are difficult to integrate together as
a complete solution
. Also, with technology changing and Jamcracker growing, Jamcr
acker has begun to
lose focus on delivering IT services that leverage web technology.

Project Scope:

Jamcracker needs to create a structured API for its service providers to
integrate their pro
ducts
. This
API will be
segregated into several
modul
es based on business function

and allow for vendor branding.
Jamcracker will also create a certification policy and procedure for vendors to follow for plugging their
product into the Jamcracker API.

**Ask Tom as to how it should be noted for Jamcracker to produce a
better vendor relationship program**

This project will be comple
ted within 18 months and cost no
more than $15 million.

Assumptions:

1)

ASPs are willing to follow the certification policy and
procedure Jamcracker develops

2)

Modules can be aligned with business functions

3)

The IT industry is very volatile and the demand for quick implementation times will only
increase.

4)

While IT personnel will be opposed to the adoption of Jamcracker’s offerings, th
e decision
making executives will be more prone to choose the time saving, cost effective offering

5)

The API developed is dynamic enough to keep up with IT industry changes
and
new technologies

6)

API will help in creating a snowball effect
relationship between

ASP

vendors and customers

**Ask Tom how to clarify this point**

7)

API creation will require a complete re
-
write of the Jamcracker product, requiring specialized
programmers.

8)

There is market demand for Jamcracker’s offering, because of lack of IT personnel w
ith proper
skills.

9)

Many
vendors that Jamcracker would integrate together with their API either don’t want to or
aren’t capable of selling directly to the end
-
user customer.

10)

Vendor working groups will be formed to b
e consulted in the design of the API str
ucture

11)

Vendor working groups will be formed to

be consulted in the creation of the certification policy
and procedure

12)

API will allow the creation of a synergistic effect between multiple vendor offerings

Constraints:

1)

Converting
customers from legacy syste
ms to Jamcracker systems

can be difficult to accomplish

2)

API modules are service integration,
data conversion,
helpd
esk support, security,
communication/collaboration, financial,
and user management

3)

The certification policy and procedure only outlines the process of ensuring the vendor product
can effectively interface with the appropriate Jamcracker API module

4)

Each API module
’s functions will be segregated from all other modules

5)

Each API module uses
open standards capable of extending the module’s functionality

6)

C
ertification policy and procedure
will be reviewed every five years, with vendor input.

7)

The API

must be fully written and ready for market within 18 months

8)

The certification policy and procedu
re must be developed within 18 months

9)

The complete project must be within a budget of $15 million

10)

The API must be developed in such a way that coincides with Jamcracker’s core competency

11)

The policy and procedure
created must adhere to Jamcracker

core values and all applicable laws

12)

The API must be written to ensure proper handling of all sensitive data

and auditable to ensure
compliancy with all regulation laws (e.g. HIPAA, SOX, GLIBA, etc.)