Amelia Bădică, Carmen Radu, Costel Ionascu Department of Statistics and Business Informatics University of Craiova, Romania 15th Workshop on Software Engineering.

Slides:



Advertisements
Similar presentations
Week 2 The Object-Oriented Approach to Requirements
Advertisements

Lecture 3 Planning and Development Methodologies.
2009 – E. Félix Security DSL Toward model-based security engineering: developing a security analysis DSML Véronique Normand, Edith Félix, Thales Research.
Chapter 2: The Database Development Process
1 Introduction to Requirements Specification. 2 Outline Requirement Engineering Software Lifecycle and Software Processes.
Using UML, Patterns, and Java Object-Oriented Software Engineering Royce’s Methodology Chapter 16, Royce’ Methodology.
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
Unit-III Requirements Engineering
2008/03/25 Unified Modeling Lanauage 1 Introduction to Unified Modeling Language (UML) – Part One Ku-Yaw Chang Assistant Professor.
Modeling Process-Oriented Integration of Services Using Patterns and Pattern Primitives Uwe Zdun and Schahram Dustdar Distributed Systems Group Institute.
Building Enterprise Applications Using Visual Studio ®.NET Enterprise Architect.
Introduction To System Analysis and Design
Knowledge Acquisitioning. Definition The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
1 COST G9 - Work group 2 meeting Székesfehérvár, Hu Modeling real property transactions Radoš Šumrada Faculty of Civil and Geodetic.
Computer Engineering 203 R Smith Requirements Management 6/ Requirements IEEE Standard Glossary A condition or capability needed by a user to solve.
IS 421 Information Systems Management James Nowotarski 16 September 2002.
IS Terms and Introductory Concepts. Contemplative Questions What is an information system? What is an information system? Why do we care about the difference.
Software Engineering CSE470: Requirements Analysis 1 Requirements Analysis Defining the WHAT.
1 IS 4420 Database Fundamentals Chapter 2: Database Development Process Leon Chen.
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
© Copyright Eliyahu Brutman Programming Techniques Course.
© 2005 by Prentice Hall 1 Chapter 2: The Database Development Process Modern Database Management 7 th Edition George Lamperti.
9 1 Chapter 9 Database Design Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
1 REQUIREMENTS ENGINEERING and SYSTEMS ANALYSIS Elements and Definitions.
IS Terms and Introductory Concepts. Contemplative Questions What is an information system? What is an information system? What is data, information and.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Welcome ISO9001:2000 Foundation Workshop.
Chapter 7: The Object-Oriented Approach to Requirements
What is Business Analysis Planning & Monitoring?
Romaric GUILLERM Hamid DEMMOU LAAS-CNRS Nabil SADOU SUPELEC/IETR.
Introduction To System Analysis and design
The Database Development Process
1 Conceptual Modeling of User Interfaces to Workflow Information Systems Conceptual Modeling of User Interfaces to Workflow Information Systems By: Josefina.
1COM6030 Systems Analysis and Design © University of Sheffield 2005 COM 6030 Software Analysis and Design Lecture 2- Software Process Models and Project.
Requirements Analysis
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Chapter 6 Requirements Engineering Process.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
Chapter 10 Information Systems Analysis and Design
Introduction To System Analysis and Design
Odyssey A Reuse Environment based on Domain Models Prepared By: Mahmud Gabareen Eliad Cohen.
Approaching a Problem Where do we start? How do we proceed?
Lecture 7: Requirements Engineering
IS Methodologies. Systems Development Life Cycle - SDLC Planning Planning define the system to be developed define the system to be developed Set the.
Modeling Shari L. Pfleeger and Joanne M. Atlee, Software Engineering: Theory and Practice, 4 th edition, Prentice Hall, Hans Van Vliet, Software.
1 Introduction to Software Engineering Lecture 1.
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
IHE Profile – SOA Analysis: In Progress Update Brian McIndoe January 18, 2011.
Object-Oriented Software Engineering using Java, Patterns &UML. Presented by: E.S. Mbokane Department of System Development Faculty of ICT Tshwane University.
FDT Foil no 1 On Methodology from Domain to System Descriptions by Rolv Bræk NTNU Workshop on Philosophy and Applicablitiy of Formal Languages Geneve 15.
What is Object-Oriented?  Organization of software as a collection of discreet objects that incorporate both data structure and behavior.
27/3/2008 1/16 A FRAMEWORK FOR REQUIREMENTS ENGINEERING PROCESS DEVELOPMENT (FRERE) Dr. Li Jiang School of Computer Science The.
1 Centre for Intelligent Systems and their Applications Division of Informatics, University of Edinburgh Draft for AKT July Workshop Jessica Chen-Burger.
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
An Agile Requirements Approach 1. Step 1: Get Organized  Meet with your team and agree on the basic software processes you will employ.  Decide how.
CS223: Software Engineering
Advances In Software Inspection
Systems Analysis Lecture 5 Requirements Investigation and Analysis 1 BTEC HNC Systems Support Castle College 2007/8.
Building Enterprise Applications Using Visual Studio®
Project Planning: Scope and the Work Breakdown Structure
Chapter 1: Introduction to Systems Analysis and Design
Business System Development
How does a Requirements Package Vary from Project to Project?
Overview of System Engineering
Introduction To System Analysis and Design PART 2
CS 8532: Advanced Software Engineering
Chapter 1: Introduction to Systems Analysis and Design
Software Design Methodologies and Testing
Chapter 1: Introduction to Systems Analysis and Design
Presentation transcript:

Amelia Bădică, Carmen Radu, Costel Ionascu Department of Statistics and Business Informatics University of Craiova, Romania 15th Workshop on Software Engineering Education, Bohinj, Slovenia, August 23-30, 2015

 Project Overview  Project Methodology  Current Status  Conclusions 15th Workshop on Software Engineering Education, Bohinj, Slovenia, August 23-30, 2015

 Organizations – very complex and require carefully developed models of their underlying business processes.  Education – an information-centered industry.  DocSys project – interested in analysis and improvement of document workflows in the University of Craiova. 15th Workshop on Software Engineering Education, Bohinj, Slovenia, August 23-30, 2015

 Provide a better understanding of the organization in order to support an increased spirit of stakeholder collaboration.  Improve the quality of processes by systematic detection of the sources and causes of poor quality.  Build a fully automated IT solution for the management of document workflows. 15th Workshop on Software Engineering Education, Bohinj, Slovenia, August 23-30, 2015

 Capture and represent process models using (semi-)formal languages.  Formalize business process knowledge and its application for the analysis, verification of workflows. 15th Workshop on Software Engineering Education, Bohinj, Slovenia, August 23-30, 2015

 Define a process design methodology.  Define an appropriate conceptual modeling framework of business processes.  Define a suitable declarative modeling language for capturing reusable process knowledge. 15th Workshop on Software Engineering Education, Bohinj, Slovenia, August 23-30, 2015

 Case processes – deal with a single instance of a unit of work = case.  Case management processes – deal with the management of the flow of cases associated to a unit of work.  Case strategy processes – take a long term view of the organization with a focus on its case and case management processes. 15th Workshop on Software Engineering Education, Bohinj, Slovenia, August 23-30, 2015

 A lot ! ◦ Methodologies ◦ Conceptual frameworks ◦ Modeling languages  Our work is mainly influenced by: ◦ RIVA methodology and Role Activity Diagrams conceptual framework (Ould, 2005) ◦ FOL-based lightweight business process modeling (Chen-Burger & Robertson, 2005) 15th Workshop on Software Engineering Education, Bohinj, Slovenia, August 23-30, 2015

 Identify the essential and designed entities that represent the business of the organization  types of documents that are circulated in the university.  Decide what business entities represent units of work for the organization  set of case and case management processes.  Define the dynamic relationships between units of work  process architecture.  Refine the dynamics of each unit of work  detailed models of each unit of work + organizational roles. 15th Workshop on Software Engineering Education, Bohinj, Slovenia, August 23-30, 2015

 Notation and example 15th Workshop on Software Engineering Education, Bohinj, Slovenia, August 23-30, 2015

 RAD – a container of roles.  Role – groups together activities into units of responsibility. A Role is defined as a directed bipartite graph with arcs connecting state nodes with action nodes (activity nodes, case refinement nodes, and part refinement nodes)  RADNode – represents a node of the directed graph that defines a given Role.  State, Activity, CaseRefinement, PartRefinement, Interaction. They define each type of node of the directed graph that represents a role.

15th Workshop on Software Engineering Education, Bohinj, Slovenia, August 23-30, 2015

metaclass(ClassName) ClassName is the name of a class (in fact a metaclass) from our conceptual framework. superclass(SuperClass, SubClass) SubClass is a subclass of SuperClass in our conceptual framework. class(MetaClass, Class) Class is a class that represents an instance of MetaClass. instance(Class, Instance) Instance is an instance of Class. Process models can be captured in our model as a set of first-order facts

 Focus on factual knowledge elicitation about UOWs addressing document circulation in the university. ◦ Inspect manually document samples ◦ Interview stakeholders for gathering information about the type, source and destination of documents  Document scope, i.e. internal or external  Generic document type, eg. request (application form), report, notification, agreement, decision, technical note, proposal, minutes,...  Document name  mission of the document.  Sample workflow instance (trace)  list of (role,activity)  Duration: 6 months 15th Workshop on Software Engineering Education, Bohinj, Slovenia, August 23-30, 2015

document( 4, internal, request, 'Studies Interruption Request', [('Faculty Student'(FacultyName),issue), ('Registry'(FacultyName),register), ('Dean(FacultyName),approve), ('Secretary'(FacultyName),execute), ('Archive'(FacultyName),archive) ] ). 15th Workshop on Software Engineering Education, Bohinj, Slovenia, August 23-30, 2015

 75 facts: Excel  CSV  Prolog  Average sample workflow instance: 6  450 activities  65 roles 15th Workshop on Software Engineering Education, Bohinj, Slovenia, August 23-30, 2015

 Verification & Validation – a complex set of activities in the software development process that are responsible with checking:  if a software complies with its specification – Verification  if it meets the real requirements of its customers – Validation. 15th Workshop on Software Engineering Education, Bohinj, Slovenia, August 23-30, 2015

 Multiple registration. ◦ A document must not be registered by more than one role belonging to the same organizational unit of the university.  Bottleneck. ◦ No role can be a bottleneck for document circulation workflows. A bottleneck role is a role that is responsible or is a decision point for an excessively high number of document circulation workflows. 15th Workshop on Software Engineering Education, Bohinj, Slovenia, August 23-30, 2015

problem('Multiple registration',DocId,DocName) :- document(DocId,_,_,DocName,SampleWorflow), member((Role1,register),SampleWorflow), Role1 \== Role2, partOf(Role1,OrganizationalUnit), partOf(Role2,OrganizationalUnit). 15th Workshop on Software Engineering Education, Bohinj, Slovenia, August 23-30, 2015

 Early stage of DocSys project at UCV  Preliminary results: ◦ Definition of the project methodology ◦ Proposal of an initial version of a process modeling conceptual framework ◦ Experiment of elicitation of factual knowledge about sample workflow instances of document circulation.  Future work: ◦ refine the gathered knowledge, by acquiring additional information that will allow us to enhance our models in order to define an automated procedure for obtaining more detailed and accurate business process models ◦ expanding our conceptual framework using concepts from BSDM, allows the knowledge engineer to capture explicit knowledge about business entities and their dependencies ◦ mapping FOL model to other languages – BPMN and OWL 15th Workshop on Software Engineering Education, Bohinj, Slovenia, August 23-30, 2015