ARCHITECTURE

OF SERVICE ORIENTED INFORMATION SYSTEMS (ASOIS)

Conf.dr.ing. Florin POP

Architecture of Service Oriented Information Systems (ASOIS)

General Information
Course teacher: Conf.dr.ing. Florin Pop
Computer Science Department, Faculty of Automatic Control and Computers
Semester: 1st Year, 1st Semester
Course hours: 28
ETCS: 6
Practical lesson: 28
Master Programs Name:
Service Engineering and Management (SEM)
Servicii Software Avansate (SSA)
Administrarea Bazelor de Date (ABD)
Evaluated activities
Course activity (1 assignment) 20%
Project 40%
Written exam 40%
Course website: http://cs.curs.pub.ro

Grading Rules
Final score of ASOIS is calculated using the following formula:

Final Grade = Exam Score + Practical Score

were:
Exam Score (max. 4p) represents the exam score for each student.
Practical Score (max. 6p) represents the sum of all activities:
o Course activity (2p). Each student will prepare an assignment on a specific topic
from course curricula.
o Project (4p). Students will design and develop an application. The project
development will involve implementations for the presented methods and examples.
Minimum requirements:
50 % of course and practical lessons activity (3 out of 6 points)
50 % of written exam (2 out of 4 points)
Final mark: obtained by rounding the total number of points.

Course activity
In the ASOIS course will be discussed issues of interest in information systems. Each student must
resolve (individually) an assignment based on themes of the course content. Teacher will propose
the assignment until week 4. The deadline for this assignment will be week 11.

Project
The project will consist of analysis, design, development and testing of information systems design
applications. Project topics will be posted via the course website and will be set in the first week.
Project topics may be proposed by students and validated by teacher. At the end of the first tree

Faculty of Automatic Control and Computer Science, University Politehnica of Bucharest

ARCHITECTURE OF SERVICE ORIENTED INFORMATION SYSTEMS (ASOIS)

Conf.dr.ing. Florin POP

weeks of the course, all students will have chosen the theme of their project; otherwise will not
receive the final score for the project. The project will be done individually and will be presented in
two phases: in the 9th or 10th week (intermediary presentation) and in weeks 13th and 14th (final
presentation).
The project represents the perfect way for the student to take an active part in exploring the subject
area, as appropriate for an advanced course. Thus, a project must be chosen that will clearly
extend your knowledge and understanding of some area of relevant to the course. Moreover, the
primary criterion for evaluating your project will be what you have learned and discovered from the
project, not the amount of work involved or the amount of code written or the number of pages of
written report. Thus, you should define your project with this strongly in mind and prepare
submissions that communicate what you have learned to the teacher. The project is also intended
as a useful prototype experience for those going on to advanced design work or research.
There are three aspects to a project: problem definition and literature background, design and
implementation and experimentation. The problem definition and literature background should
explore and describe the problem or area of interest and provide some investigation of background
work in this area. It should examine the research literature in the selected area, according to what
are the important problems, to what degree are these problems understood and solved, how do
different solutions interrelate, and what are the important issues for the future. Original thoughts,
solutions, insights are strongly encouraged and will be rewarded. Because of the time limits of the
quarter and our emphasis on software implementation, this stage is generally expected to be very
limited, e.g. Google around, read a couple of papers, think hard for awhile and write your project
proposal. The design should try to map out a software solution that is implementable with the
available time and computer resources. With the intended "prototyping" nature of the projects,
design, implementation and evaluation may be performed iteratively. In the implementation and
experimentation phase, the design, or some aspect of the design is implemented to demonstrate
feasibility. The experimentation involves developing a reasonable hypothesis and designing and
performing an experiment to test this hypothesis.
All work submitted should be done in a professional manner as though you were being paid for it.
Documents should be typewritten and use good technical English. Software submitted for credit
should be well written, meeting reasonable standards of programming.

Final exam
The exam will consist of a 3 test subjects. The first issue (2p) will treat a theoretically topic
presented in class. The other two issues will have an applicative character through their offering
solutions to specific problems course. The third topic will be chosen from two proposed topics. The
exam will be scheduled at the end of the term (in exam session) at a date to be agreed between
students and teacher.

Faculty of Automatic Control and Computer Science, University Politehnica of Bucharest