project approach to software development

Project approach to software development

Sanja Čandrlić, [email protected]

Martina Ašenbrener, [email protected]

About the presentation

• A short overview of educational model in area of business software development

• This model provides basic knowledge in business process analysis, data modeling, reading models, participation in software development teams

• Related to several courses at undergraduate and graduate level

• Department of Informatics University of Rijeka• Experiences

213th Workshop SE Education and Reverse EngineeringBansko

Introduction

• Project approach is common in software industry • At faculty level – experiencing and understanding activities

and phases during software development• Following chosen methodology


The basic idea

• To give an overview of IS and SW development phases • To teach each develoment phase in a separate course in

detail

• A group of courses was developed• Knowledge about strategic planning, process modeling, data

modeling, programming, ...

• Verification and validation?


MIRIS

• Methodology for Information System Development• Metodologija za razvoj informacijskih sustava• Basic hypothesis – system decomposition• It prescribes phases of development and activities within a

particular phase, defines relations between particular activities and sequence of activity execution

• 1984 ..... published 1995


MIRIS (2)

• MIRIS uses 3 basic methods: data modeling method, process modeling method and application modeling method


Logical modeling - design

Phase 1: STRATEGIC PLANNING OF IS

Phase 2: MAIN PROJECT

Phase 3: PROJECT REALIZATION

Physical modeling – building

Phase 4: SOFTWARE REALIZATION

Phase 5: IMPLEMENTATION AND APPLICATION

Phase 6: MAINTENANCE

Why?

What?

How?

Information systems course

• 2nd year of undergraduate study• Introduction to IS and SW development• MIRIS methodology in detail, other methodologies• Practical part – seminar about a chosen IS

– front office of a bank, insurance agency, ...– pharmacy – shipyard– store – city library– ...


Information systems course (2)

• Gathering and analysis of documents used in the system (internal, input, output)

• Analysis and understanding of the data in each document• Invoice, invoice number

• The first step in analysis; starting point for the courses that follow


data exampledata type and

lengthdescription

Invoice number

2013-232 S10the year the invoice is issued in and the ordinal number of the invoice in that year

Process modeling course

• 3rd year of undergraduate study (winter sem.)• Related to the second phase of the development• To perform interviews and meetings with the representatives

from inside the system• Structured Systems Analysis


Process modeling course (2)

Student papers include:•Data flow diagrams (several levels)•Context diagram•Hierarchy of the system representation diagrams – function tree of the processes•Process description

More detailed view of the business system:•An abstract model of the entire system•Deviding of the system into subsystems•Models of subsystems


Data modeling course

• 3rd year of undergraduate study (summer sem.)• Related to the third phase prescribed by MIRIS• Entity – relationship method

Student papers are complex data models based on the documents gathered:

• Entity – relationship diagrams• Relationship representation of the database

• Improved for final papers and final exams


Introduction to software engineering course

• 3rd year of undergraduate study• Practical part - the basis for further work on SW

development• To use the capablities of the chosen CASE tool for business

SW development• The development itself will take place in the SE course one

year later• Programming in several other courses independently


Software engineering course

• 1st year of graduate study• More professional view on business systems• Implementation of the knowledge about models,

metamodeling, design of SW specification, cost analysis, team SW development

• Presentation of student SW applications• Teams can compare their independent work


Information system of an organisation course

• 2nd year of graduate study• Design of SW architecture model • The method for modeling called Software Product

Architecture (APP – Arhitektura Programskog Proizvoda)• An original method relying on DFD and ER methods • Capability to estimate the best solution for a business

application


Strategic planning of IS course

• 2nd year of graduate study• First phase of SW development, according to MIRIS• Taught later because of its complexity - students have to

„grow”• The importance of working with users• Defining the priorities of a business system, establishing the

need for further IS development • Identifying gaps in the process and estimating business

applications level of support to business processes ....


Conclusion – list of courses

• Information systems course – Mandatory course at the 2nd year of undergraduate study

• Process modelling course– Mandatory course at the 3rd year of undergraduate study

• Data modelling course– Mandatory course at the 3rd year of undergraduate study

• Introduction to SE course – Elective course at the 3rd year of undergraduate study

• SE course– Mandatory/elective course at the 1st year of graduate study

• Strategic planning of IS course– Mandatory/elective course at the 2nd year of graduate study

• IS of an organisation course– Elective course at the 2nd year of graduate study


Conclusion – list of assignments

• Choosing a company and analyzing their documents

• Process model: data flow diagrams, process tree, process analysis

• Data model – entity relationship diagrams• Software specification, cost analysis • Software architecture model• Business application development• Priorities and process analysis


Conclusion

• The task of SW development is divided, parts studied through several courses

• SW development during several semesters• Feeling of accomplishement• The final result is complex and made with complete

understanding• Option – do it all in one or two courses – fast and

superficial


• Thank you for your attention!

• Questions?


project approach to software development

Documents