P. 1
E Business Implementation

E Business Implementation

|Views: 106|Likes:
Published by Koutarapu Ramesh

More info:

Published by: Koutarapu Ramesh on May 18, 2012
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less






  • Part One Project management phases
  • Structuring an e-business project
  • 1.1 E-business project management
  • 1.2 The project planning phase
  • 1.3 The requirements gathering phase
  • 1.4 The solution research phase
  • 1.5 The high-level design phase
  • 1.6 The detailed design phase
  • 1.9 Implementation phase
  • 1.10 Handover phase
  • 1.11 Project documentation
  • Resourcing an e-business project
  • 2.1 Selecting project staff
  • 2.2 When to deploy project staff
  • 2.3 Obtaining project staff
  • Part Two E-business technology phases
  • The five phases of e-business adoption
  • Phase 1:Internet-based e-business publishing
  • 4.1 Key technologies used
  • 4.2 Types of publishing systems
  • 4.3 Custom Internet and Intranet publishing systems
  • 4.3.1 Key technologies used
  • 4.3.2 High-level designs of Internet and Intranet systems
  • 4.3.4 Vendors of Internet and Intranet software
  • 4.4 Portal systems
  • 4.4.1 Key technologies used
  • 4.4.2 High-level designs for portal systems
  • 4.4.3 Benefits and limitations of portal solutions
  • 4.4.4 Vendors of portal solutions
  • 4.5 Content management systems
  • 4.5.1 Key technologies
  • 4.5.2 High-level designs of content management systems
  • 4.5.3 Benefits and limitations of content management systems
  • 4.5.4 Vendors of content management systems
  • Phase 2:Transacting with customers
  • 5.1 Key technologies used
  • 5.2 High-level designs for transactional e-business solutions
  • 5.3 Benefits and limitations of transactional e-business systems
  • 5.4 Vendors of transactional e-business systems
  • Phase 3:Internal enterprise application integration
  • 6.1 Key technologies used
  • 6.2 Point-to-Point point EAI solutions
  • 6.3 Middleware solutions
  • 6.4 Application server middleware solutions
  • 6.4.1 High-level design of application server middleware solutions
  • 6.4.2 Benefits and limitations of application server middleware solutions
  • 6.4.3 Vendors of application server middleware solutions
  • 6.5 Hub and spoke middleware solutions
  • 6.5.1 High-level design of hub and spoke middleware solutions
  • 6.5.2 Benefits and limitations of hub and spoke middleware solutions
  • 6.5.3 Vendors of hub and spoke middleware solutions
  • Table 6.2Vendors of hub and spoke middelware solutions
  • 6.6 Message bus middleware solutions
  • 6.6.1 High level design of message bus middleware solutions
  • 6.6.2 Benefits and limitations of message bus middleware solutions
  • 6.6.3 Vendors of message bus middleware solutions
  • Table 6.3Vendors of message bus middleware solutions
  • Phase 4:External integration
  • 7.1 Key technologies used
  • 7.2 Customized solutions
  • 7.3 Extended EAI solutions
  • 7.3.1 Vendors of extended EAI solutions
  • 7.4 Supply chain management solutions
  • 7.4.1 Vendors of supply chain management solutions
  • Table 7.2 Vendors of supply chain management solutions
  • 7.5 Marketplace solutions
  • 7.5.1 Vendors of marketplace solutions
  • Table 7.4Vendors of marketplace solutions
  • 7.6 Business process integration solutions
  • 7.6.1 High-level designs of business process integration solutions
  • 7.6.2 Benefits and limitations of business process integration solutions
  • 7.6.3 Vendors of business process integration products
  • Phase 5:Dynamic e-business and web services
  • 8.1 Key technologies used
  • 8.1.1 Process management and internal integration
  • 8.1.2 Business intelligence systems
  • 8.1.3 High-level design of internal and external BPI solution
  • 8.1.4 Benefits and limitations of dynamic e-business
  • 8.1.5 Vendors of dynamic e-business solutions
  • 8.2 Web services
  • 8.2.1 Key technologies used
  • 8.2.2 Benefits and limitations of dynamic e-business using web services
  • 8.2.3 Vendors of web services solutions
  • Table 8.2Vendors of web services solutions
  • Part Three E-business supporting technologies
  • Critical technologies supporting e-business
  • E-business development technologies
  • 10.1 Key technologies used
  • 10.4 Microsoft .NET
  • Hardware platforms and operating systems
  • 11.1 Key technologies used
  • 11.2 Types of hardware platforms
  • 11.3 Hardware platform performance
  • 11.4 High-level designs of hardware platform architectures
  • Security
  • 12.1 Corporate information technology security policies
  • 12.2 Key technologies used
  • 12.3 Layered security systems
  • 12.3.1 Network layer security
  • 12.3.2 Operating system layer security
  • 12.3.3 Data layer security
  • 12.3.4 Application layer security
  • 12.3.5 Access control mechanisms
  • 12.3.6 Security auditing and monitoring
  • 12.4 High-level designs of security systems
  • 12.5 Vendors of security solutions
  • Networking systems
  • 13.1 Key technologies used
  • 13.2 The corporate IP address allocation scheme
  • 13.3 Network hardware
  • 13.4 High-level designs for networking systems
  • 14.1 Key technologies used
  • 14.2 High-level designs for corporate DNS systems
  • 14.3 Vendors of DNS systems
  • Open Source technologies
  • 15.1 Key technologies used
  • 15.3 The Open Source development approach
  • 15.4 Open Source software projects
  • 15.5 Benefits and limitations of Open Source technologies
  • Summary and conclusion
  • References
  • Index

Following project handover and completion, documentation is required as a
knowledge repository for the project, and for the developments of subsequent
versions of the e-business system requested by users. In such cases, the
documentation provides a detailed understanding of decisions that were made,
and the manner in which technologies were implemented, to ensure they do not
introduce problems into stable live production systems.

Due to their role in designing and implementing the solution, the e-business
technical architect has overall responsibility for the creation and delivery of
projecttechnical documentation. Similarly, the non-technical project documentation
is the responsibility of the project manager. Non-technical project documentation
includes documents concerned with the ongoing management of the complete
project by the project manager such as training plans, the project risk register,
meeting minutes between project members and company staff, budgets, and the
project plan.

E-business Implementation


The completed documentation should include all outputs created during the
projectlifecycle. These include the project initiation document, the scope
document, the design documents, test plans and test results, installation and
configuration documents, and support and training documents. It should also
include the source code repository maintained throughout the project.

The project Iinitiation document introduces the reasons for beginning the
project,and suggests a proposed solution. These issues are covered through an
introduction to the project consisting of an overview of the business issues
facingthe company, and a general discussion of the high-level business and
technical requirements for the project. The discussion of the proposed solution
should cover project management and technical aspects, including the preliminary
project plan, budget, an assessment of staff skills required for delivering the
proposed technology solution, and a preliminary timeframe for the project.

The scope document provides the detailed context to why the project is required
and what it should deliver. It expands on the overview of business issues facing
the company to include the detailed requirements of all project stakeholders,
including internal stakeholders within the company and external users and partner
and supplier companies. Requirements are gathered from relevant company and
customer sources, divided into business and technical requirements, and
summarizedthrough a requirements analysis matrix. Arisk management register
also accompanies the scope document detailing the risk issues facing the
project and risk management plan to cope with these.

The high-level design document provides an overview of the proposed solution.
It should incorporate the functional design components, which describe the
groups of features provided in the solution, and corresponding operational
design components, which describe products and technologies chosen to supply
these features. The vendors and product evaluation and selection criteria
determinedduring the research phase may also form part of the high-level
design, or be included as a supporting document for complex projects with large
numbers of requirements to satisfy.

The detailed design documents describe the blueprint to build the solution
through detailed functional and operational design components. Detailed
functionaldesign elements include software components, their interactions and
interfaces, which are expressed using detailed UMLuse cases, data models, and
component class model diagrams. Detailed operational elements in this design

Structuring an e-business project


include descriptions of infrastructure systems such as hardware server systems,
network systems, security systems, and specific deployment configurations,
which are expressed using UMLdiagrams, network diagrams, and installation,
configuration and operation documents for each operational system. The
detailed design documents also describe the source code management tool
deployed in the project, and the change management processes used to maintain
the solution source code and project documents.

The test plan documents detail the testing procedures and tools used during the
build phase. These include the test scripts used to test individual components
against their intended design, test scripts for communication between components
using specified interfaces, and test scripts for the correct functioning of the
complete solution against the design specifications and stakeholder requirements.
Each test script also includes documented results of each phase of testing.

The installation and configuration documents allow staff members to recreate
the solution from its constituent functional and operational components. These
include installation processes for operational components such as servers,
networkdevices, development systems, security systems, and software. They
also include the subsequent configuration of these once they have been
installed, such as performance tuning, load balancing configuration and security
hardening, and the setting of run-time parameters.

Finally, the support documents should detail the operational management and
support processes and tools required for the ongoing operation of the solution.
These include software management systems, such as HPOpenView, and their
appropriate configuration, and daily operational processes such as diagnosis
and problem resolution, content migration, or security checking processes.
Support documents are created during the pilot phase by project staff, in
consultationwith company support staff. Once the project enters the
implementationphase, support documents are refined to accommodate
additional supportand management requirements discovered during this

E-business Implementation


You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->