Internet Services - Modelling and Developing

Analysis report

• The name of the project
• The authors of the report
• The date
• The index of contents

Description of the present situation of the company or organization

The description of the present situation gives to the reader a picture of the company or of the organization the analysis is concerning with.

Overview of the company

The overview of the company includes as well the description of the business field and the amount of employees in the company. It may also include the history of the company if it has some relevance in the present situation of the company.

External partners

You would investigate and describe the external partners of the company. You may illustrate the verbal description by a diagram of the external partners. If the company has lots of external partners, you can group them for example by roles or business fields.

Customers

The description of present and potential customers of the company may include the segmentation of the customers. The electronic commerce maturity model may be deepen the picture of the level of the customers' Internet behaviour.

Competitors

The description of the competition situation includes the list and characteristics of the competitors. The competitors may be named but they may also be described as roles without names.

Information 

You would write out a list of the information the business requires. Typical business information includes the customer, the product and the order. You would list the most significant attributes of the information as well. It is recommended to use the UML object-class-model to describe the business information, but, if you like, you may also use the entity-relationship-model. 

The model includes both the diagram and the appropriate verbal explanation.

According to the UML-notation the picture of an object class includes the name, the attributes and the services of the object class.

The object class diagram includes the object classes, their attributes and services, and the structures between object classes which are associations, hierarchies and aggregates.

Processes

You should choose the level with which you describe the processes of the company. The reader should get the idea of the processes of the company but you should not burden him or her by too small detalies. If the company has a lot of processes, you should group them somehow. 

It is recommended to use the UML use-case-model to describe the business processes, but, if you like, you may also use the hierarchial process-model.

The use-case-diagram describes the use-cases and their actors. An actor may be also an other application and in that case you could use a symbol of the equipment instead of the stick figure.

Information security architecture, policy and rules

You should describe the architecture, policy and rules of the information security in the present situation - if there are any.

Risks of the present situation (risk-analysis)

You should list and analyse the risks of the company's present situation. You may use a table in the risk-analysis.

Business strengts, weaknesses, opportunities and threats (the SWOT-analysis) 

The SWOT-analysis describes the business strengts, weaknesses, opportunities and threats. You may use in your description a two-by-two-table with the bullets in the cells. It is recommended to  characterize them verbally and argue for them.

Problems and their possible solutions (the problem-solution-analysis)

You should analyse the problems of the present business and seek to find some solutions for them. You may use the fish-bone-method and present the results in a table.

Business requirements

The business requirements are based on the description of the present situation and especially on the problem-solution-analysis, because the latter describes the requirements to solve the present problems. The requirements may be grouped by actors, for example the requirements of customers, the requirements of marketing, the requirements of production and so on. It is recommended to find out the different actors' shared requirements and put them in the priority order.

Goal situation

Definition of the goal

The definition of the goal should be short and clear. The goal situation should be based on the business requirements.

Measures

You would define some concrete measures to proof that the goal situation has been reached. The measures should have numbers describing the total or relative amount or the dead-lines. According this kind of measures you are able, in some specific time, to prove, if the goal has been achieved.

External partners

Will the company's external partners be the same in the goal situation as they are in the present situation or will there be some changes?

Customers

Will the company's customers be the same in the goal situation as they are in the present situation ?

Competitors

Will the company's competitors be the same in the goal situation as they are in the present situation? How should the goal situation influence on the competition situation? 

Information 

Will the company's business information be the same in the goal situation as it is in the present situation? Usually, if the business field stays the same, the business information do not change considerably. 

Processes

Will the company's processes be the same in the goal situation as they are in the present situation? Usually the processes will change somehow with each adoption of a new information system.

Information security architecture, policy and rules

Will the company's information security architecture, policy and rules be the same in the goal situation as they are in the present situation? The business activity in the net will have new information security risks and, thus, requires some modifications on the company's information security architecture, policy and rules.

Risks of the goal situation (risk-analysis)

You should list the risks of the goal situation and analyse them.