Cracow University of Economics

Department of Computational Systems

Course: Analysis and Design of Information Systems

Project title:

Major:
Studies type: Full time/Extramural

Project team (ex. No.):

Authors Names Group No. Index No.

Academic year:
Semester:
Version summary:

Version: Short description Date:

ex. Introduction; Models of processes, Requirements
ex. 1.0, 1.2, 2.1, 3.0 specification; Data dictionary, Complete project 0000-00-00
Detailed document description and authors roles:
Members of the team : (a)
Part of the document (b): Action description(c):
1)
2)
3)
4)
5)
6)

Attention:
The project documentation is created in several iterations (according to the course outline).
The table containing the document version summary is mandatory for each iteration. A
separate table is created for each version of the document (tables of all versions must be
cumulatively included in the document). Each iteration ends with a full version of the
document (emailed to the moderator).
(a) In the same order as at the cover page; in the case of lack of activity leave the empty row.
(b) Chapter number (with possibly additional information) - one chapter may be created by many
members (and even should be).
(c) Typical actions: creating, modifying, correcting, formatting, preparing drawings (diagrams),
etc., with additional scope information (ex. creating a business justification)

Files name should be created according to the following rule:

ADIS-ENG-Team_number-Document_Version.pdf (ex. ADIS-ENG-1-2_0.pdf)

The comments in the template (blue text) should be removed in the version you will send for
assessing.
 IS project: ENG, academic year, team No.

Table of Contents
1 Introduction....................................................................................................................................4
1.1 Company Profile.....................................................................................................................4
1.1.1 Description of the organization's activities.....................................................................4
1.1.2 Market description.........................................................................................................4
1.2 Business strategy....................................................................................................................4
1.2.1 Strategy..........................................................................................................................4
1.2.2 Goals hierarchy...............................................................................................................4
1.3 Preliminary study....................................................................................................................4
1.3.1 Possibilities study............................................................................................................4
1.3.2 Alternatives evaluation...................................................................................................4
1.4 Feasibility study......................................................................................................................4
1.4.1 Project objectives definition...........................................................................................4
1.4.2 Scope of the project........................................................................................................5
1.4.3 Project and IS conditions and constrains........................................................................5
1.4.4 Performance analysis......................................................................................................5
1.4.5 Feasibility conclusions and recommendations...............................................................5
1.5 General scope of the project..................................................................................................5
2 Logical specification of the system.................................................................................................6
2.1 Models....................................................................................................................................6
2.1.1 Company map.................................................................................................................6
2.1.2 Business process models................................................................................................6
2.1.3 Business process logic description..................................................................................6
2.2 Requirements specification....................................................................................................6
2.2.1 Business requirements...................................................................................................6
2.2.2 Users groups identification.............................................................................................6
2.2.3 Users requirements........................................................................................................7
2.3 Data dictionary.......................................................................................................................7

Page 3 of 7
 IS project: ENG, academic year, team No.

1 Introduction
1.1 Company Profile
Here put a brief company profile.

This point as a whole describes the company, its business sector, size, resources, capabilities,
market position, etc. The level of detail description must be sufficient to understand the
overall business situation and the premises of the action taken.
1.1.1 Description of the organization's activities
What does the company do, what is the scope of its activities, what is the daily functioning of
the organization. What are the problems and what are the possibilities of the organization
(rationale for the project).
1.1.2 Market description
Market of the company: customer characteristics, competition, environment (close and
distance).

1.2 Business strategy

Point as a whole includes a description of the strategy and definition of business goals and
objectives.
1.2.1 Strategy
Description of the strategy
1.2.2 Goals hierarchy
Indication of the strategic, tactical and operational objectives; relation among the goals and
objectives (hierarchy, goals tree) - the size of the structure depends on the size of the
organization and the complexity of the adopted development strategy. Goals and objectives
should be SMART.

1.3 Preliminary study

This point includes a problem identification and possible solutions, analysis of the
effectiveness of possible solutions, assumptions, etc.
1.3.1 Possibilities study
Answer to the question about the possibility of achieving the goals. Identify possible options
for achieving these goals (with a preliminary analysis of outlays, threats, etc.). Justification
for the purpose of continuing the activities or proposing their abandonment (postponement)
1.3.2 Alternatives evaluation
Details of the expected results of the project. Description of the adopted evaluation criteria
of the alternatives (along with the reasons for the choice of assessment methods). Detailed
description of the alternatives together with their evaluation according to the adopted
criteria. Solution recommendation together with a justification and a proposal of further
activities (or a suggestion of abandonment or postponement of activities).

1.4 Feasibility study

Page 4 of 7
 IS project: ENG, academic year, team No.

1.4.1 Project objectives definition

Clarification of the objectives of the information system project.
1.4.2 Scope of the project
A detailed description of the scope of the work covering all the work required to
achieve the objectives.
1.4.3 Project and IS conditions and constrains
Assumptions about the market situation, outlays, business opportunities, execution
time, etc., together with justification and definition of boundary conditions.
Overview of project constraints: financials, time, technical, organizational,
knowledge, skills and attitudes of people, legal and political (if applicable).
1.4.4 Performance analysis
Analysis of the effectiveness of the adopted variant using the methods presented in
the classes.

1.4.5 Feasibility conclusions and recommendations

What will affect the feasibility of the project? What hazards have to be considered
during the project and during the operation of the system? Final conclusion about
project budget and time.

1.5 General scope of the project

Assuming that, in the accepted implementation scenario, the work or part thereof will be
delegated to a dedicated team (ex. an external company), this subsection defines in detail
what the team will be responsible for (in the case of an outsourcer, it will be the scope of
work to be included in the contract / contract / - what is the contractor doing and what is the
result?). This is a general level, so we do not provide technical details unless they are part of
the requirements to contractors in their selection process. The description clearly defines all
the results of the planned project, including: products (ex. software, auxiliary materials, etc.),
activities (ex., training - who, where, how, when, etc.; installation), supplies (ex. computer
hardware, software tools, etc.). In this section, we also point out all exclusions (ie, products
or activities that are necessary to achieve desired objectives but do not enter into project
scope and will be implemented by someone else).

Page 5 of 7
 IS project: ENG, academic year, team No.

2 Logical specification of the system

Based on the previously defined general scope of the project, this chapter describes the
project at a level of detail that allows you to estimate the required resources (time, costs,
people, etc.). The logical specification of the system is a general description of the
architecture and its main components. This is not a complete Specification of Requirements,
but a description of the system's functionality and its features.

2.1 Models
All models should be performed in Adonis. You need to deliver models in ZIP file with a
generated HTML (automatically compressed to ZIP format) it should contain company map +
7 detailed business process models/diagrams. You don’t need to put any content in points:
2.1, 2.1.1, 2.12.
2.1.1 Company map
The company map contains all grouped processes (at a higher level of organization) that
take place in the client organization and the links between these processes. This is a
hierarchy of processes (business areas). In the company map you should indicate (ex. use
different color) those processes that are directly related to the IS project. Company map
should be incorporated in separate ZIP file.
2.1.2 Business process models
Business process models show in detail the sequence of actions to be taken to achieve the
specific effect and interdependence (relations) between these activities. Include 7 process
models directly related to the IS project. Business process models should be incorporated in
separate ZIP file.
2.1.3 Business process logic description
You should include 3 processes (algorithms) using 3 methods introduced during classes
(decision table, decision tree, structured English). You should put these 3 models in that
documentation.

2.2 Requirements specification

2.2.1 Business requirements
Specification of requirements at the business level. The requirements should be presented in
a structured list.
2.2.2 Users groups identification
Identify and structure all stakeholders groups (not only direct users) and analyze their
influence on project development and system operations. Groups should be identified
according to the pattern presented during classes.

Page 6 of 7
 IS project: ENG, academic year, team No.

2.2.3 Users requirements

Specification of the requirements on the user level; in a detailed way define what the
application should do. Non-functional requirements (referring to software parameters and
quality) could be also included. Each of the user requirements should be presented in the
form of a table:
Requirement Id.: Descriptive name

Description: Detailed description of user requirement

Remarks: Indication of conditions (ex. standards, regulations or rules that must be fulfilled) and
possible dependencies with other user requirements.

Reference: Ids of business requirements Users: User Id.

2.3 Data dictionary

The data dictionary is to define the data items according to the rules discussed during classes. The
dictionary should contain at least 70 entries. The entries in the dictionary should be alphabetically
ordered.

Page 7 of 7