Documente Academic
Documente Profesional
Documente Cultură
1
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Context
No enterprise can long exist without a business or mission i.e. it must produce product(s)
or service(s) desired by a customer(s). It usually must also produce these products or services in
competition with other enterprises also vying for this same business.
Problem
There are only two basic classes of functions involved in operating any enterprise:
1. Those involved in operating the processes which result in producing the “product” which
fulfills the enterprise’s mission.
2. Those involved in the “control” of the mission in an “optimal” manner to achieve the
necessary economic or other gains that assure the viability or continued successful
existence of the enterprise. These comprise the collection, storage and use of information
concerning the business processes in order to control them.
Thus it includes all management, planning, and scheduling, control, and data
management functions. Information or data will undergo multiple transformations i.e. many
separate task in fulfilling the information-handling requirements for an enterprise system. These
transformations or tasks are usually successive operations forming sets of sequential and parallel
networks.
All enterprises, of whatever type, follow a “life cycle” from their initial concept in the
mind of an entrepreneur through a series of stages or phases comprising their development,
design, construction, operation and maintenance, refurbishment or obsolescence, and eventually
to their final disposal.
2
Department of Computer Engineering
Vishwakarma Institute of Technology-37
1. BPD: System developer will develop the BPDs according to the need that are captured from
the customer that will identify the implicit and explicit requirements.
2. BPMN: It provides business with capability of defining and understanding their internal
and external business procedures through BPD that will give organizations the ability to
communicate these procedures in a standard manner. Without business process modeling,
you might pick wrong piece of business to automate & implicit requirements may not be
captured.
3. RE: In Software Engineering, Requirement Analysis encompasses all of the tasks that go
into the instigation, scoping and definition of a new or altered system. Requirement
engineers and business analysts, along with software developers, identify the needs or
requirements of a customer.
4. UML: A notation that allow developer to specify, visualize and construct artifacts of
software system.
Solution
Once the integration of all of the informational and customer product and service
functions of an enterprise has been well-planned, the actual implementation of such integration
may be broken into a series of coordinated projects. All tasks will be defined in a modular
fashion, along with their required interconnections. These tasks will be implemented in a
3
Department of Computer Engineering
Vishwakarma Institute of Technology-37
modular fashion, again permitting their later substitution by other different methods of carrying
out the same function.
2. Information Storage - the retention of information and data for periods of time (specified or
indeterminate) for use in later actions of the Information Architecture components. Storage may
be in human-readable form (written - libraries, etc.) or machine-readable (databases or related
depositories).
As a part of Process Capture and Modeling three models are considered as follows:
Activity models: They describe which activities have to be executed within processes,
which restrictions concerning the order of these activities have to be respected, and how
these activities are implemented.
Object models: They describe the types of objects created and manipulated within
processes.
Organization models: They describe, in which organizational context a process is
supposed to take place (including roles).
A Context Level Domain Model can describe related systems in a domain. This can reduce
the time needed for developers to learn the modeling language, since it can use familiar terms
and concepts. The Context Level Domain Model can cover a range of abstraction levels for a
particular domain.
4
Department of Computer Engineering
Vishwakarma Institute of Technology-37
INTERACTION FRAMEWORK
UML MODELER
Figure Abbreviations:
BPD : Business Process Diagram
BPMN: Business Process Modeling
Notation
BI : Business Intelligence
NM : Notation Manager
RG : Requirement Gathering
RC 5
: Requirement Collection
RM : Requirement Manager Department of Computer Engineering
Vishwakarma Institute of Technology-37
Benefits
6
Department of Computer Engineering
Vishwakarma Institute of Technology-37
7
Department of Computer Engineering
Vishwakarma Institute of Technology-37
INTRODUCTION
This document provides the purpose of the feasibility study, the background of the
proposed project, the methodology used for performing the study, and any reference materials
used in conducting the feasibility study for the project titled “Integrated Modeling Framework
for Enterprise System”.
Integrated Modeling Framework for Enterprise System is a CASE tool that supports a
Software Architecture, Enterprise Framework (EF). Such frameworks expose a rich set of
semantics and modeling paradigms for developing and extending enterprise applications.
Integrated Modeling Framework for Enterprise System uses a Meta Model Driven approach to
model engineering. The model captures the business logic and lifecycle semantics of the
component. This approach truly facilitates the "model once run anywhere" paradigm.
Purpose
No enterprise can long exist without a business or mission i.e. it must produce product(s)
or service(s) desired by a customer(s). It usually must also produce these products or services in
competition with other enterprises also vying for this same business.
8
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Methodology
The following methodologies were used to conduct the feasibility study for this system
includes the study of the feasibility of implementation of the new features that are going to be
incorporated in the system. Below are some of the Features and the methodologies used for these
features implementation in the current systems:
4. UML: A notation that allow developer to specify, visualize and construct artifacts of
software system.
5. DOMAIN: Domain performs the task of building domain modeler and structuring
of domain information. It also includes building a task of domain vocabulary and
provide domain model notation. It performs task association of domain models.
9
Department of Computer Engineering
Vishwakarma Institute of Technology-37
In governing processes on the basis of models it is ensured that real-world processes behave as
specified in their models. In most existing workflow management approaches only unstructured
pieces of information, like documents and images, can be managed. That means, processes that
create and manipulate structured pieces of information cannot be supported properly.
General Information
The various UML CASE tools available like Enterprise Architect, Vp_Uml Suite,
Rational Rose etc. provide support for the functionality of the UML model of a system, which
captures aspects from requirements to deployment in varying degrees. These CASE tools aid
UML diagramming within a development process.
Rational Rose doesn’t support features of UML 2.0 which are provided in the case tools
like Enterprise Architect, Vp_Uml suite. Requirement Modeling is done using Use Case
mapping in all the above Tools. Features of Use case Mapping, NFR Mapping is not provided by
any of these tools. Enterprise Architect and Rational Rose generate code using Class Diagrams
while Vp_Uml generated it using State Chart Diagram. Diagram mapping to images in BMP,
WFM is supported by Enterprise Architect and Rational Rose. Vp_uml suite along with these
supports JPG, JPEG formats. The CRC card support is not available in Rational Rose and
Enterprise Architect while is there in Vp_Uml Suite.
System Objective
Requirements are indicated for workflow languages through workflow patterns. Patterns
address requirements in an imperative workflow style expression, but are removed from specific
workflow languages. The primary task of a workflow management system is to enact case-driven
processes by allowing workflow models to be specified, executed, and monitored. Workflow
process definitions are defined to specify which activities need to be executed and in what order.
10
Department of Computer Engineering
Vishwakarma Institute of Technology-37
An elementary activity is an atomic piece of work. Workflow process definitions are instantiated
for specific cases (i.e. workflow instances). Activities are connected through transitions and we
use the notion of a thread of execution control for concurrent executions in a workflow context.
Further mapping the activity diagrams to workflow modeling and then use Petri nets to analyze
the workflow so modeled. Then UML Modeler with the help of the notation manager models the
diagrams namely, Use Case, State Chart, Activity and Class Diagram and creates a workspace
for the same. The Notational Compliance will be for UML 2.0.
ISSUES
Workflow Specification:
Workflow specifications in a broad sense have number of different perspectives. The
workflow perspective describes activities and their execution ordering through different
constructors, which permit flow of execution control, e.g. sequence, splits, parallelism and join
synchronization. Activities in elementary form are atomic units of work, and in compound form
modularize an execution order of a set of activities. The resource perspective provides an
organizational structure anchor to the workflow in the form of human and device roles
responsible for executing activities.
Specification language:
All WFMS’s of which we are aware provide graphical workflow specification languages.
In addition, many WFMS’s provide rule-based or constrained workflow specification languages.
These languages are higher-level languages than standard programming languages such as C and
C++. They support the specification of the following:
• Task structure (control flow) and information exchange between tasks (dataflow) in a
workflow, e.g., specifying that tasks can be executed in parallel, or that a task needs to wait for
data from other tasks).
• Exception handling, e.g., specifying what actions are necessary if a task fails or a workflow
cannot be completed.
• Task duration, e.g., specifying initiation and completion time of a task
• Priority attributes, e.g., specifying priorities for task scheduling
11
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Alternatives
A brief comparison between these available tools and Integrated Modeling Framework for
Enterprise System
Documentation Html, RTF Html, RTF Html, RTF, Html, RTF, PDF
PDF, MsWord
Mapping
Diagrams as BMP, WMF BMP, WMF JPG, JPEG, JPG, JPEG, BMP
Images BMP
12
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Comparisons of alternatives
1. Programming Language
The comparison for programming language was done among Microsoft Visual
Basic 6.0, Microsoft .NET Framework, and Java 2 Second Edition.
Microsoft Visual Basic and Microsoft .NET framework are not free to use while
Sun Java is a free offering from Sun CORP. Ltd. Also Sun Java consists of a set of API’s that
can be used for the development of any application. Besides its own API’s there are several
open source organizations that develop API’s for Java. The integration of these interfaces is
fairly simple and the most striking feature of this language was that it allowed portability of
applications developed in Java while the other two did not support platform independency.
For Borland’s JBuilder Personal Edition, basic IDE plus a few additional tools such as a GUI
designer, integrated JUnit framework, and some other items required for application
development comes at a cost. Eclipse is a free, open-source IDE. The most popular of all the
Java IDE, but harder to set up and configure than the commercial ones. Eclipse is the base
IDE, but there are many Java-related plug-in for Eclipse, and several commercial IDE built
on top of Eclipse.
Hence, Sun Java Studio was finalized over the other two.
3. Databases
The databases that were considered for the system are Oracle, MySQL, Microsoft
Access and XML database. Oracle is the industry preferred database and contains everything
an application needs. But it has a lot of dependencies, is too heavy to be used in this
application. MySQL is a free open source database, is very light, fast and efficient and a
worthy candidate to be considered for this application. Microsoft Access feature wise not
much different from either Oracle or MySQL, comparatively lighter than Oracle. But its only
disadvantage is that it is a proprietary and its usage requires heavy licensing fees.
Another tool considered data storage is to use XML databases. XML can be
extended to be used as databases. The primary advantage of using XML as database is that it
13
Department of Computer Engineering
Vishwakarma Institute of Technology-37
does not require any system specific configuration which supports the cause of the system to
be platform independent. Another, it can modified in the way we need it. It is also extremely
light. The only disadvantage of using XML as database is that, if the number of entries in the
database increases, it tends to slow down.
To support that the entire system is feasible from the point of view of
development, the following recommendations and conclusion has been chalked out. The
Platform Independency of Java made it a preferable choice over all the other considerations
as the language of implementation. The free availability of Sun Java Studio to the members
of Sun Microsystems along with no plug-ins required made it a preferred choice.
For the Database selection though MySQL had better features than XML,
but the fact that XML does not require any configuration and MySQL needs to be
configured differently for different platforms, favored XML.
Thus all the recommended tools are platform independent and are free of
cost. Thus to conclude the above, this report has examined the feasibility of the system
“Integrated Modeling Framework for Enterprise System”.
14
Department of Computer Engineering
Vishwakarma Institute of Technology-37
15
Department of Computer Engineering
Vishwakarma Institute of Technology-37
OVERVIEW
Various tools are available in market but none are as useful as Integrated Modeling
Framework for Enterprise System uses a Meta model driven approach to model engineering it
separates the definition of the business logic from implementation. The model captures the
business logic and lifecycle semantics of the component. As such, this approach truly facilitates
the "model once run anywhere" paradigm.
The users for the system will be every Enterprise or an organization that follows the
UML standard. The system is being developed independently by four students as Final Year
Project in Computer Engineering for University of Pune. The expected time required for the
completion of this system is one year.
Project Goals
16
Department of Computer Engineering
Vishwakarma Institute of Technology-37
17
Department of Computer Engineering
Vishwakarma Institute of Technology-37
PROJECT SCOPE
Included
The system does not guarantee that the framework generated shall be 100% accurate. The
system will provide a framework according to its semantics knowledge gathered from
requirements and some diagrams, for the user to build the system from that point onwards.
1. WFM: System will perform workflow checking according to the workflow traceability.
System administrator will schedule the workflow. A workflow consists of a sequence of
connected steps. It is a depiction of a sequence of operations, declared as work of a person, a
group of persons, an organization of staff, or one or more simple or complex mechanisms.
2. BPMN: It provides business with capability of defining and understanding their internal
and external business procedures through BPD that will give organizations the ability to
communicate these procedures in a standard manner. Without business process modeling, you
might pick wrong piece of business to automate & implicit requirements may not be
captured.
3. RE: In Software Engineering, Requirement Analysis encompasses all of the tasks that go
into the instigation, scoping and definition of a new or altered system. Requirement engineers
and business analysts, along with software developers, identify the needs or requirements of a
customer.
4. UML: A notation that allow developer to specify, visualize and construct artifacts of
software system.
5. DOMAIN: Domain performs the task of building domain modeler and structuring of
domain information. It also includes building a task of domain vocabulary and provide domain
model notation. It performs task association of domain models.
18
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Excluded
19
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Deliverables
Identifier Deliverable Planned Receiver
Date
BPDM Business process diagram Manager System Developer
RM Requirement Manager Project Managers,
Requirement
Engineers
SM Security Manager Requirement
Engineer
UM UML Generator System Analysts,
System Developers
DM Domain Modeler System Developers
WFM Workflow Manager System Analysts,
System Developers
20
Department of Computer Engineering
Vishwakarma Institute of Technology-37
21
Department of Computer Engineering
Vishwakarma Institute of Technology-37
INTRODUCTION
It gives an idea to the developers and its user on what the system will shape up like and
the functions the system will perform. This document also introduces all the functionalities
that the system can perform and its effect on the users and the stakeholders. Survival for the
enterprise depends on the ability to continually refine and alter the elements of its business
and organization. Such changes may represent attempts to refine existing practices, or more
radical alterations to the mission of the enterprise.
The rationale of this document is to collect, analyze and define high-level needs and
features of the Integrated Modeling Framework for Enterprise Systems. It focuses on the
capabilities needed by the enterprise and customer, and why these needs exist. The details of
how the Integrated Modeling Framework for Enterprise Systems fulfils these needs are
detailed in the use-case and supplementary specifications.
The intended audiences for this SRS are requirement engineers, system
developers, system analysts and project managers. Requirement Engineers play a major role
in the system as everything they specify in the requirements, forms the base on which the rest
of system functionalities depends. The system uses these requirements to model various
UML diagrams. They form the core of the system. System Developers need to work around
with the requirement engineers and system analyst assisting them, so that when development
process begins it becomes easy for them to understand the system and perform their task in
an efficient manner.
Purpose
No enterprise can long exist without a business or mission i.e. it must produce product(s)
or service(s) desired by a customer(s).The purpose of this document is to introduce aspects
for developing an integrated framework for an enterprise systems.
Intended Audiences
Enterprise:
Customers:
This group is end user with restricted rights.
Developer:
It is community which actually develops the framework
Designer:
One whose design must meet the requirements specified in this SRS.
22
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Tester:
This community tests the system according to the test cases.
SCOPE
Database:
These comprise the collection, storage, manipulation and use of information
concerning the business processes in order to control them.
Framework:
Software framework: A reusable set of libraries or classes for a software system
(or subsystem).
Application framework: A software framework used to implement the standard
structure of an application for a specific operating system
Web application framework: A software framework for development of dynamic
websites, web applications and web services
Workflow Management
Build workflow editor to perform abstraction of requirements
Build workflow planner to select appropriate set of available resources
Build workflow observer to monitor progress
Build workflow engine to carry out ordered of workflow task.
Requirement Management
Build requirement query system
Perform traceability
Build Change control system
Conversion of requirements
Requirement report generation
Organizing metamodel
Meta model creation
Metamodel generation
Metamodel maintenance
Metamodel integration
Document Linking
Generation of XMI DTD
Generate repository for model instances
Generate grammar for models
XMI documentation
23
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Realization of CBD
Build concurrency adaptor
Solve concurrency interface conflict
Carry out component based development.
Code assembly.
Benefits
24
Department of Computer Engineering
Vishwakarma Institute of Technology-37
References
1.A New Approach to Version Control, 3rd March 1993, IEEE Software Transactions
1. Mapping User Requirements to Implementations, January 1995, IEEE Software Journal
2. Software Reflexion Models - Bridging the Gap between Design and Implementation, 4th
April 2001, IEEE Transactions on Software Engineering
3. Reviewing Software Diagrams - A Cognitive Study, 2nd February 2004, IEEE
Transactions on Software Engineering
4. Guided Development with Multiple Domain-Specific Languages, Anders
5. Hessellund, Andrez Wasowski, IT University of Copenhagen, Denmark.
6. An eXecutable Metamodelling Facility for Domain Specific Language Design,
7. Tony Clark, Andy Evans, Paul Sammut, James Willians.
8. Domain Specific Models, Model Analysis, Model Transformation, Tivadar
9. Szemethy, August 2006, Nashville, Tennesse.
10. Visualizing Model Mapping in UML. Jan Hendrik Hausmann and Stuart Kent
11. A Model Transformation Framework for the Automated Building of Performance Models
from UML Models_ Andrea D’Ambrogio
12. MOF QVT final adapted Specification by OMG
13. Jean-Jacques Dubray, “A Novel Approach for Modeling Business Process Definitions,”
2002
14. BPMN Adopted Specification 3
15. http://www.ebpml.org/ebpml2.2.doc
16. Response to OMG BPD RFP, OMG, Sept. 2003, bei/03-08-02
17. http://www.omg.org
25
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Overview
Section 1
Introduces you to the system as a whole, its capabilities and how it is different from other tools.
It describes the scope of the system being developed and the references that were needed to give
a shape to this system.
Section 2
It Describes the Product’s Perspective, the various Interfaces of the system, its functions, user
characteristics, constraints, assumptions and dependencies.
Section 3
This section describes external interfaces to the system, performance requirements, design
constraints, system attributes and system specific requirements.
Section 4
The supporting information makes the SRS easier to use. It includes: Table of Contents at the
front of the document Index Appendices.
Overall Description
Integrated Modeling Framework for Enterprise System is a CASE tool. Its main intention
is to provide a framework on which models will be generated, which will result in enhanced
design and in turn improved productivity of the systems the end-users build.
Providing a strong and reliable base to the models in the form of requirements.
26
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Problem Statement
Product Perspective
1. Requirement Engineering
Requirements elicitation,
Requirements analysis and negotiation,
Requirements specification,
System modeling,
Requirements validation,
Requirements management.
27
Department of Computer Engineering
Vishwakarma Institute of Technology-37
2. UML
Unified Modeling Language is popular for its diagrammatic notations. We all know
that UML is for visualizing, specifying, constructing and documenting the components of
software and non software systems. Block of the system provides the user with the
facility to model diagrams and provides with the notations for various UML diagrams
such as Use Case, State Chart, Activity and Class Diagram, etc
3. WFM
4. BPMN
This block performs the task of interweaving the requirements from both RE and BPD
and analyzing the requirements for identifying probable Use Cases and Actors. It then
generates the SCD and RCD based on its analysis.
5. Domain
Domain performs the task of building domain modeler and structuring of domain
information. It also includes building a task of domain vocabulary and provide domain
model notation. It performs task association of domain models.
28
Department of Computer Engineering
Vishwakarma Institute of Technology-37
INTERACTION FRAMEWORK
UML MODELER
Figure Abbreviations:
BPD : Business Process Diagram
BPMN: Business Process Modeling
Notation
BI : Business Intelligence
NM : Notation Manager
RG : Requirement Gathering
RC : Requirement Collection
RM : Requirement Manager
29
Department of Computer Engineering
Vishwakarma Institute of Technology-37
System Interfaces
This section describes the various system interfaces required for realization of this CASE tool.
30
Department of Computer Engineering
Vishwakarma Institute of Technology-37
User Interfaces
User Interfaces defines the various interfaces available for the end-user to interact with the
system.
Help System
A complete detailed Help system made available to the end-user of the system will contain all
the support information the end-user requires in case of some difficulties in using the system
arises. Help allows the user to walk through pictorial presentation of all the functionalities of the
system. Some of the highlights of the help system are as follows:
Pictorial Presentation
Search
Additions
1. This tool will allow user to add notes, search, add project packages.
2. Diagrams can be embedded in Document. Supporting formats are: GIF, BITMAP.
3. Tools and notational help will be provided to the user.
Software Interfaces
The development of the system on the Java platform gives an added advantage of having the
support of large number of Open Source Libraries to be used within the system. These libraries
are tried and tested and will help in quick development of the system.
JFreeReport
This library supports exporting of reports in tabled format to various file formats such as PDF,
XLS, etc. Report generation activity will use this library.
JavaHelp
JavaHelp library API’s are intended for generating help for authors, information architects, and
software developers who need a framework for delivering online help and documentation.
The xmlenc library is a stream-based XML output library for the Java programming
language, Microsoft XML Core Services (MSXML) is a set of services. XSD (XML Schema
Definition) XSDs are far more powerful than DTDs in describing XML languages. They use a
rich data typing system and allow for more detailed constraints on an XML document's logical
structure. XSDs also use an XML-based format, which makes it possible to use ordinary XML
tools to help process them.
31
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Hardware Constraints
Memory Constraints
The application being developed in Java has the following memory constraints
1. Java application tends to run slightly slow because they run inside the JVM. This lag can be
reduced by efficient coding and avoiding use of heavy components.
2. The product development on the latest beta version of the Java Development Kit Version 6
Codenamed Mustang. At the time of writing, this beta release is more memory demanding
and is expected to cool down by the time its final version is released.
Considering the above factors the memory requirements for the product is as follows:
Operations
Workflow Management
Workflow Management (WFM) promises to provide a suitable infrastructure for the execution of
business processes in a distributed environment. WFM aims at the automation of business
processes. Workflows can be characterized as executable images of business processes. Business
processes describe and explain how a business is conducted; therefore, more business related
terms are used in their definitions. Workflows are executable objects. Workflow management
promises to cope with this requirement by providing a highly dynamic execution platform for
multi-faceted business processes.
32
Department of Computer Engineering
Vishwakarma Institute of Technology-37
This includes:
Requirement Management
Adding requirement, validating them, if required, making changes, updating requirements are
some of the major activities here. Besides, various traceability options and version viewing
facilitates the requirement engineers. Comparing requirements for ambiguity and analyzing the
impact of the requirements on the system are the other major activities supported in the
Requirement management.
Organizing metamodel
The metamodel driven architecture joins together the business model and the metadata captured
in the "meta" levels of the business model to bring about new levels of abstraction,
personalization, and extensibility of these business models – essential ingredients to manage
business information (content) and application/business processes that use this content. This
includes metamodel creation, metamodel generation, maintenance and meta model integration.
33
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Product Functions
Model diagram
1. Deliver diagram controls
2. Generate diagram profiles
Manage security Maintain Profiles 1. Maintain login
2. Manage profile right
34
Department of Computer Engineering
Vishwakarma Institute of Technology-37
User Characteristics
System Analyst
Systems analysts apply mathematical methodology to the analysis of the systems involved
trying to form a detailed overall picture. Here Petri nets mathematics is used to convert the
activity diagrams into systematic code generation via workflow design.
Requirement Engineers
The requirement engineers are expected to determine whether or not the new system is feasible,
schedulable, affordable, legal and ethical. In Enterprise Modeling tool requirements are gathered
via textual analysis. This allows requirement engineers to understand needs efficiently. It also
provides support for accommodating changing requirements via iterative modeling approach.
Requirements Log
Requirements log holds the Requirement generation pattern. This are transferred to requirement
overview diagram and given as input to use case profile will be stored in the XML database in
35
Department of Computer Engineering
Vishwakarma Institute of Technology-37
the form of .rqs file. Every project will have one requirement file physically, but logically there
will one requirement file for every requirement.
User Information
The system level login will contain all the users who belong to that organization. The user won’t
be able to login to a project unless and until he is given permission to do so. All the users
working on a particular project are stored in the .prj file.
Login
At the most basic level login based security will be provided. An authenticated user can login to
the system and thus access the projects assigned to that user. To get a login id and password, the
user should contact the central administrator, who has the rights to assign new users to the
system and also remove the users from the system.
Digital Signatures
At file level, Digital Signature security will be provided. If any file that has been tampered in any
way outside the system’s environment the digital signature check will be failed. This will prevent
errors in the project from external sources
36
Department of Computer Engineering
Vishwakarma Institute of Technology-37
37
Department of Computer Engineering
Vishwakarma Institute of Technology-37
38
Department of Computer Engineering
Vishwakarma Institute of Technology-37
39
Department of Computer Engineering
Vishwakarma Institute of Technology-37
40
Department of Computer Engineering
Vishwakarma Institute of Technology-37
41
Department of Computer Engineering
Vishwakarma Institute of Technology-37
42
Department of Computer Engineering
Vishwakarma Institute of Technology-37
43
Department of Computer Engineering
Vishwakarma Institute of Technology-37
44
Department of Computer Engineering
Vishwakarma Institute of Technology-37
45
Department of Computer Engineering
Vishwakarma Institute of Technology-37
4 21. Process
System explicit
will create requirements
a new workspace.
22. Validate explicit requirements
16.
5 New workspace will be store workspace to db.
23. Store database
17.
6. System
24. Display
will generate
messageantoacknowledgement
user for a user.
18. Check sequence flow
DESCRIPTION Step Alternate Course of Action
1 System user will request for workspace.
46
Department of Computer Engineering
Vishwakarma Institute of Technology-37
47
Department of Computer Engineering
Vishwakarma Institute of Technology-37
48
Department of Computer Engineering
Vishwakarma Institute of Technology-37
49
Department of Computer Engineering
Vishwakarma Institute of Technology-37
50
Department of Computer Engineering
Vishwakarma Institute of Technology-37
51
Department of Computer Engineering
Vishwakarma Institute of Technology-37
4 37. Process
System explicit requirements
will determine requirement overlaps.
38. Validate explicit requirements
28.
5 System willdatabase
39. Store save requirements to requirement db.
29.
DESCRIPTION 40. Display message Alternate
Step 30. to user Course of Action
Check sequence flow
1 User will propel requirements.
52
Department of Computer Engineering
Vishwakarma Institute of Technology-37
53
Department of Computer Engineering
Vishwakarma Institute of Technology-37
54
Department of Computer Engineering
Vishwakarma Institute of Technology-37
55
Department of Computer Engineering
Vishwakarma Institute of Technology-37
2 1. Process
BPD_ managerexplicit requirements
will Process explicit requirements.
2. Validate explicit requirements
3 BPD_ manager validate explicit requirements.
3. Store database
4 BPD _ db willmessage
4. Display store profile to db.
to user
56
Department of Computer Engineering
Vishwakarma Institute of Technology-37
2 49. Process
BPD_ explicit
manager requirements
retrieve notations from db.
50. Validate explicit requirements
37.
3 BPD_ manager will check sequence flow.
51. Store database
38.
4 BPD _ manager
52. Check
Display will apply
message BI_ rules.
to user
39. sequence flow
5 System will store project to BPD db.
57
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Secondary Actors BPD db, BPD Notation db, BPD requirement db.
58
Department of Computer Engineering
Vishwakarma Institute of Technology-37
59
Department of Computer Engineering
Vishwakarma Institute of Technology-37
60
Department of Computer Engineering
Vishwakarma Institute of Technology-37
5 62. Validate
System
46. explicit
will store requirements
domain in domain_ db.
63. Store database
47.
6. System will send an acknowledgement to the user.
64. Check
48. Display messageflow
sequence to user
DESCRIPTION Step Alternate Course of Action
1 User will send request to modify domain.
61
Department of Computer Engineering
Vishwakarma Institute of Technology-37
5 65. Process
System explicitdomain
will display requirements
model notations to user.
66. Validate explicit requirements
DESCRIPTION Step 49. Alternate Course of Action
1 67. Store database
50. will request for edit notations (notation name).
User
68. Check
51. Display messageflow
sequence to user
2 Domain _manager will accept user request.
62
Department of Computer Engineering
Vishwakarma Institute of Technology-37
63
Department of Computer Engineering
Vishwakarma Institute of Technology-37
64
Department of Computer Engineering
Vishwakarma Institute of Technology-37
3 Meta model manager will extract requested meta model from meta-model
db.
65
Department of Computer Engineering
Vishwakarma Institute of Technology-37
66
Department of Computer Engineering
Vishwakarma Institute of Technology-37
67
Department of Computer Engineering
Vishwakarma Institute of Technology-37
68
Department of Computer Engineering
Vishwakarma Institute of Technology-37
69
Department of Computer Engineering
Vishwakarma Institute of Technology-37
70
Department of Computer Engineering
Vishwakarma Institute of Technology-37
71
Department of Computer Engineering
Vishwakarma Institute of Technology-37
72
Department of Computer Engineering
Vishwakarma Institute of Technology-37
73
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Scenario Description
74
Department of Computer Engineering
Vishwakarma Institute of Technology-37
75
Department of Computer Engineering
Vishwakarma Institute of Technology-37
76
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Scenario Description
77
Department of Computer Engineering
Vishwakarma Institute of Technology-37
78
Department of Computer Engineering
Vishwakarma Institute of Technology-37
79
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Scenario Description
80
Department of Computer Engineering
Vishwakarma Institute of Technology-37
81
Department of Computer Engineering
Vishwakarma Institute of Technology-37
82
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Scenario Description
83
Department of Computer Engineering
Vishwakarma Institute of Technology-37
84
Department of Computer Engineering
Vishwakarma Institute of Technology-37
85
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Scenario Description
86
Department of Computer Engineering
Vishwakarma Institute of Technology-37
87
Department of Computer Engineering
Vishwakarma Institute of Technology-37
88
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Scenario Description
89
Department of Computer Engineering
Vishwakarma Institute of Technology-37
90
Department of Computer Engineering
Vishwakarma Institute of Technology-37
91
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Scenario Description
92
Department of Computer Engineering
Vishwakarma Institute of Technology-37
93
Department of Computer Engineering
Vishwakarma Institute of Technology-37
94
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Scenario Description
95
Department of Computer Engineering
Vishwakarma Institute of Technology-37
96
Department of Computer Engineering
Vishwakarma Institute of Technology-37
97
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Scenario Description
98
Department of Computer Engineering
Vishwakarma Institute of Technology-37
99
Department of Computer Engineering
Vishwakarma Institute of Technology-37
100
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Scenario Description
101
Department of Computer Engineering
Vishwakarma Institute of Technology-37
102
Department of Computer Engineering
Vishwakarma Institute of Technology-37
103
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Scenario Description
104
Department of Computer Engineering
Vishwakarma Institute of Technology-37
105
Department of Computer Engineering
Vishwakarma Institute of Technology-37
106
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Scenario Description
107
Department of Computer Engineering
Vishwakarma Institute of Technology-37
108
Department of Computer Engineering
Vishwakarma Institute of Technology-37
109
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Scenario Description
Alternate Course of
Action [ ACA ]
1. User will request for (search model).
2. System will authenticate user.
3. Meta- model controller will extract requested meta model.
4. System will associate meta-model model.
5. System will return message to GUI.
6. GUI will display model.
7. System will show an acknowledgement to user.
110
Department of Computer Engineering
Vishwakarma Institute of Technology-37
111
Department of Computer Engineering
Vishwakarma Institute of Technology-37
112
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Scenario Description
Alternate Course of
Action [ ACA ]
1. User will request for (search meta model).
2. System will authenticate user.
3. Meta-model controller will acquire transformation rules.
4. System will employ meta-model transformation.
5. System will store result to meta-model db.
6. System will return message to user.
113
Department of Computer Engineering
Vishwakarma Institute of Technology-37
114
Department of Computer Engineering
Vishwakarma Institute of Technology-37
115
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Scenario Description
Alternate Course of
Action [ ACA ]
1 Administrator will search workflow model.
2. System will authenticate user.
3. System will accommodate changes manually.
4. Perform workflow check on workflow model by user itself.
5. Reply model to GUI.
6. Administrator will stores result to model db.
116
Department of Computer Engineering
Vishwakarma Institute of Technology-37
117
Department of Computer Engineering
Vishwakarma Institute of Technology-37
118
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Scenario Description
Alternate Course of
Action [ ACA ]
1. User will request search workflow model.
2. System will check workspace elements.
3. System will forward elements.
4. System will determine and accommodate changes.
5. System will store changes to model db.
6. Workflow db will reply to GUI.
7. System GUI will send an acknowledgement to user.
119
Department of Computer Engineering
Vishwakarma Institute of Technology-37
120
Department of Computer Engineering
Vishwakarma Institute of Technology-37
121
Department of Computer Engineering
Vishwakarma Institute of Technology-37
122
Department of Computer Engineering
Vishwakarma Institute of Technology-37
123
Department of Computer Engineering
Vishwakarma Institute of Technology-37
124
Department of Computer Engineering
Vishwakarma Institute of Technology-37
125
Department of Computer Engineering
Vishwakarma Institute of Technology-37
126
Department of Computer Engineering
Vishwakarma Institute of Technology-37
127
Department of Computer Engineering
Vishwakarma Institute of Technology-37
128
Department of Computer Engineering
Vishwakarma Institute of Technology-37
129
Department of Computer Engineering
Vishwakarma Institute of Technology-37
130
Department of Computer Engineering
Vishwakarma Institute of Technology-37
131
Department of Computer Engineering
Vishwakarma Institute of Technology-37
132
Department of Computer Engineering
Vishwakarma Institute of Technology-37
133
Department of Computer Engineering
Vishwakarma Institute of Technology-37
134
Department of Computer Engineering
Vishwakarma Institute of Technology-37
135
Department of Computer Engineering
Vishwakarma Institute of Technology-37
136
Department of Computer Engineering
Vishwakarma Institute of Technology-37
137
Department of Computer Engineering
Vishwakarma Institute of Technology-37
138
Department of Computer Engineering
Vishwakarma Institute of Technology-37
139
Department of Computer Engineering
Vishwakarma Institute of Technology-37
140
Department of Computer Engineering
Vishwakarma Institute of Technology-37
141
Department of Computer Engineering
Vishwakarma Institute of Technology-37
142
Department of Computer Engineering
Vishwakarma Institute of Technology-37
143
Department of Computer Engineering
Vishwakarma Institute of Technology-37
144
Department of Computer Engineering
Vishwakarma Institute of Technology-37
145
Department of Computer Engineering
Vishwakarma Institute of Technology-37
146
Department of Computer Engineering
Vishwakarma Institute of Technology-37
147
Department of Computer Engineering
Vishwakarma Institute of Technology-37
148
Department of Computer Engineering
Vishwakarma Institute of Technology-37
149
Department of Computer Engineering
Vishwakarma Institute of Technology-37
150
Department of Computer Engineering
Vishwakarma Institute of Technology-37
151
Department of Computer Engineering
Vishwakarma Institute of Technology-37
152
Department of Computer Engineering
Vishwakarma Institute of Technology-37
153
Department of Computer Engineering
Vishwakarma Institute of Technology-37
154
Department of Computer Engineering
Vishwakarma Institute of Technology-37
CLASS DIAGRAM
155
Department of Computer Engineering
Vishwakarma Institute of Technology-37
1. CRC TEMPLATE #1
Responsibilities Collaborators
156
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Responsibilities Collaborators
157
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Responsibilities Collaborators
158
Department of Computer Engineering
Vishwakarma Institute of Technology-37
4. CRC TEMPLATE #2
Responsibilities Collaborators
159
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Characteristics Tangible.
Subclass NONE.
Responsibilities Collaborators
160
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Responsibilities Collaborators
161
Department of Computer Engineering
Vishwakarma Institute of Technology-37
7. CRC TEMPLATE #3
162
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Responsibilities Collaborators
163
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Responsibilities Collaborators
164
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Responsibilities Collaborators
165
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Responsibilities Collaborators
166
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Responsibilities Collaborators
167
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Responsibilities Collaborators
168
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Responsibilities Collaborators
169
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Services
1) Process explicit requirement.
2) Validate explicit requirement.
3) Store db.
4) Create BPD.
5) Forward to database.
6) Accept implicit requirement.
7) Process requirement.
8) Save requirement.
Responsibilities Collaborators
170
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Responsibilities Collaborators
171
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Characteristics Tangible.
Subclass NONE.
Responsibilities Collaborators
172
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Responsibilities Collaborators
173
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Responsibilities Collaborators
1)Display Search Result()
2)Display Error message () Model db.
3)Get Model Details() Meta-model db.
4) Edit Model ()
5)Generate Meta-model()
6)Extract Meta-model()
7)Display Model()
8)Accept New Meta-model()
9) Built Meta-model()
174
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Responsibilities Collaborators
175
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Responsibilities Collaborators
176
Department of Computer Engineering
Vishwakarma Institute of Technology-37
177
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Characteristics Tangible.
Subclass NONE.
Responsibilities Collaborators
1) Acquire Workflow Details() Domain db.
2) Associate notations() Notation db.
3) Check element relationships() Model db.
4) Schedule Workflow
178
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Responsibilities Collaborators
1) Acquire Workflow Details() Domain db.
Notation db.
2) Manage Workflow () Model db.
3) Check Traceability()
4) Process Model()
5) Evaluate domain()
179
Department of Computer Engineering
Vishwakarma Institute of Technology-37
180
Department of Computer Engineering
Vishwakarma Institute of Technology-37
181
Department of Computer Engineering
Vishwakarma Institute of Technology-37
182
Department of Computer Engineering
Vishwakarma Institute of Technology-37
IF profile=found
THEN display profile at GUI
End if
Terminate
ELSE
ELSE
GET metamodel
SEARCH model and metamodel from model db
RETRIEVE model and metamodel
TRANSFORM metamodel and store changes
IF model=found
THEN Search model into model db
ADD model to model db
STORE model changes
DISPLAY notation
ADD notation to profile db
IF notation added successfully
THEN exit from profile
ELSE repeat
183
Department of Computer Engineering
Vishwakarma Institute of Technology-37
End if
IF build==Successful
DISPLAY confirmation done
ELSE
Show error message
Terminate
OPEN GUI editor and display models
DISPLAY new model
SEND Acknowledgement to user
End if
Terminate
184
Department of Computer Engineering
Vishwakarma Institute of Technology-37
185
Department of Computer Engineering
Vishwakarma Institute of Technology-37
REQUEST Profile
SYSTEM accepts notations request
IF profile==VALID
THEN
ENTER profile details
SEARCH profile in profile db
IF Profile=found
THEN display profile names to user
ELSE Display error message
End if
GOTO create_new_profile
RETRIEVE profile from UML profile db
MODIFY profile
ADD new notations
186
Department of Computer Engineering
Vishwakarma Institute of Technology-37
187
Department of Computer Engineering
Vishwakarma Institute of Technology-37
188
Department of Computer Engineering
Vishwakarma Institute of Technology-37
189
Department of Computer Engineering
Vishwakarma Institute of Technology-37
190
Department of Computer Engineering
Vishwakarma Institute of Technology-37
ELSE
CREATE new Workspace
ELSE
Get the details from the user
PROCESS details
ASSOCIATE Workspace details
EXTRACT subject, verb, and object from the requirements
CATOGOREIZE details
TOKENIZE details
UPDATE changes in UML db
SAVE changes in UML db
DISPLAY the details
ENDIF
191
Department of Computer Engineering
Vishwakarma Institute of Technology-37
192
Department of Computer Engineering
Vishwakarma Institute of Technology-37
193
Department of Computer Engineering
Vishwakarma Institute of Technology-37
194
Department of Computer Engineering
Vishwakarma Institute of Technology-37
195
Department of Computer Engineering
Vishwakarma Institute of Technology-37
196
Department of Computer Engineering
Vishwakarma Institute of Technology-37
197
Department of Computer Engineering
Vishwakarma Institute of Technology-37
198
Department of Computer Engineering
Vishwakarma Institute of Technology-37
PROVIDE metamodel
Terminate
ELSE
Terminate
199
Department of Computer Engineering
Vishwakarma Institute of Technology-37
200
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Terminate
201
Department of Computer Engineering
Vishwakarma Institute of Technology-37
202
Department of Computer Engineering
Vishwakarma Institute of Technology-37
203
Department of Computer Engineering
Vishwakarma Institute of Technology-37
204
Department of Computer Engineering
Vishwakarma Institute of Technology-37
205
Department of Computer Engineering
Vishwakarma Institute of Technology-37
206
Department of Computer Engineering
Vishwakarma Institute of Technology-37
207
Department of Computer Engineering
Vishwakarma Institute of Technology-37
208
Department of Computer Engineering
Vishwakarma Institute of Technology-37
209
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Continue
Modify requirements
STORE the requirements in requirement db
UPDATE requirement db
ELSE
ACCEPT explicit requirements
IF requirements = PRESENT
PRINT requirements already exists
ELSE
Continue
PROCESS explicit requirements
SAVE requirements
GENERATE implicit requirements
PROCESS requirements
STORE implicit requirements
UPDATE requirements db
CREATE BPD
SAVE BPD in BPD db
UPDATE BPD db
DISPLAY BPD
ENDIF
210
Department of Computer Engineering
Vishwakarma Institute of Technology-37
211
Department of Computer Engineering
Vishwakarma Institute of Technology-37
212
Department of Computer Engineering
Vishwakarma Institute of Technology-37
213
Department of Computer Engineering
Vishwakarma Institute of Technology-37
214
Department of Computer Engineering
Vishwakarma Institute of Technology-37
215
Department of Computer Engineering
Vishwakarma Institute of Technology-37
ELSE
DISPLAY domain not found
ELSE
DISPLAY invalid request
216
Department of Computer Engineering
Vishwakarma Institute of Technology-37
ENDIF
217
Department of Computer Engineering
Vishwakarma Institute of Technology-37
218
Department of Computer Engineering
Vishwakarma Institute of Technology-37
ELSE
DISPLAY invalid request
ENDIF
219
Department of Computer Engineering
Vishwakarma Institute of Technology-37
220
Department of Computer Engineering
Vishwakarma Institute of Technology-37
ENDIF
END Provide Domain Model Notation
221
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Resources 1) Model_db
2) Meta-model_db
Interactions Extract and transform Model and Meta-model.
Interface/Exports Accept request from user
1) Model extraction window.
2) Meta-model transformation window.
222
Department of Computer Engineering
Vishwakarma Institute of Technology-37
223
Department of Computer Engineering
Vishwakarma Institute of Technology-37
224
Department of Computer Engineering
Vishwakarma Institute of Technology-37
225
Department of Computer Engineering
Vishwakarma Institute of Technology-37
ENDIF
END Extract Meta-model
226
Department of Computer Engineering
Vishwakarma Institute of Technology-37
227
Department of Computer Engineering
Vishwakarma Institute of Technology-37
228
Department of Computer Engineering
Vishwakarma Institute of Technology-37
229
Department of Computer Engineering
Vishwakarma Institute of Technology-37
230
Department of Computer Engineering
Vishwakarma Institute of Technology-37
231
Department of Computer Engineering
Vishwakarma Institute of Technology-37
232
Department of Computer Engineering
Vishwakarma Institute of Technology-37
233
Department of Computer Engineering
Vishwakarma Institute of Technology-37
234
Department of Computer Engineering
Vishwakarma Institute of Technology-37
235
Department of Computer Engineering
Vishwakarma Institute of Technology-37
The main aim is to provide separate profile to user. The various UML profiles are
distinguished from each other and to maintain them precisely. The two objectives are:
i. Organize notations Profile.
ii. Incorporate Meta-model.
1.1 Organize Notation Profile: Various UML profile has different notation. This objective
performs the task of unraveling the notations as per the UML Profile. It takes care of
notations do not get combine with one another.
1.2 Incorporate Meta-model: The UML profile has diverse models and diagrams. Thus every
model has a meta-model. So newly generated models will have their Meta-model and it
needs to get added into the database.
2. MANAGE SECURITY
The authentication of the user is performed in manage security. Along with that, it also
maintains the user profile. So that the users work is safe. The two major objectives of it are:
i. Maintain Profile.
ii. Allocate Workspace.
1.1 Maintain Profile: To provide security to the user. It authenticates the user and provides it
workspace. Thus user can maintain it profile as per required and secure his work.
1.2 Allocate Workspace: To provide workspace to new user. To generate the necessary work
environment for user. So that the profile of does not get mix-up with other.
3. ORGANIZE META-MODEL.
The major job is to organize the Meta-model whenever they are modeled in the diagram
by the user. It not only organizes the meta-model but maintains them. The objectives are:
i. Provide Meta-model.
ii. Model diagram.
1.1 Provide Meta-model: The Meta-model of various models are associated with it as per the
diagrams. Also the notations required for generating the diagram are retrieved and
manipulated.
1.2 Model Diagrams: Modeling diagram perform the task of providing the diagram
controllers. It generates the notations that are must for the diagram profile selected.
236
Department of Computer Engineering
Vishwakarma Institute of Technology-37
4. MANAGE REQUIREMENT
This goal deals with requirement provided by user and analyze them. This will perform the
management of the requirement and also differentiating them. The two objectives to achieved
are:
i. Capture Requirement.
ii. Trace Requirement.
1.1 Capture Requirement: the requirements are provided by the user, these requirements are
acquired and stored. After that the requirements are categorized into respective classes.
1.2 Trace Requirement: An important operation of analyzing ambiguity i.e. determines if any
uncertain requirement is present or not, also it verify that requirement are present in
database are not.
5. MANAGE BPD
This goal is providing the Business Process Diagrams for developing the model. This
helps to provide the distinguishing notations required for generating the diagram or model.
The major two objectives are:
i. Develop BPD.
ii. Process BPD.
1.1 Develop BPD: The objective is providing the BPD notations as per the needs captured.
The diagrams will be formulated using the Business Intelligence rules provided by BPD.
1.2 Process BPD: The requirements will be classified into implicit and explicit. That is
helpful for providing the correct BPD for the respective requirement.
This is one of the important goal of all as it is necessary for formulating of any domain. It
holds the necessary vocabulary and the structure information for developing the domain. The
objectives are as follows:
i. Build Domain.
ii. Provide Domain Model Notations.
1.1 Build Domain: It provides the foundations for formulating any domain. It supplies the
structure information required to develop a specified domain. It offers the necessary
domain vocabulary for the domain.
1.2 Provide Domain Model Notations: Its work is to provide the required notations that are
must for the generation of the domain model and associate the domain notations with
models.
237
Department of Computer Engineering
Vishwakarma Institute of Technology-37
1.1 Extract Meta-Model: Every model has its own Meta-model, so when a new model is
build the meta-model is needed to be transformed. Thus the meta-Model are extracted
for same purpose.
1.2 Transform Meta-model: The extracted Meta-models are transformed into the new Meta-
model with the help of Transformation rules
.
The goal deals with the verification of the workflow of diagram. The model should be
correctly associated with the elements. Its objectives are as follows:
i. Schedule Workflow.
ii. Build Workflow Traceability.
1.1 Schedule workflow: The check is performed the flow of elements is in correct sequence.
Also the relation associated with elements is valid or not.
1.2 Build Workflow Traceability: Trace the changes that occur during the workflow. It also
accommodates the changes in workflow.
238
Department of Computer Engineering
Vishwakarma Institute of Technology-37
239
Department of Computer Engineering
Vishwakarma Institute of Technology-37
TEST PLAN
1. PURPOSE
The purpose of this test plan is to describe the scope, features to be tested and not to be
tested, and items to be tested, criteria, approach, and deliverables included in testing activities for
this particular project. The aim of this document is to guide through the testing procedure.
Through unit testing, individual components of the system will be tested independently to
ensure their quality, and to uncover errors in data structures, program logic, program structure,
interfaces and functions and operations of a component.
Through integration testing, group of dependent components will be tested together to ensure
the quality of design and construction of software architecture, integrated functions or operations
at sub-system level and interfaces and interactions between them.
Through system testing software will be tested as a whole. It will test system functions,
performance and system reliability.
OUTLINE
2. Introduction
Integrated Modeling Framework for Enterprise System is a CASE tool that supports a
Software Architecture, Enterprise Framework (EF). Such frameworks expose a rich set of
semantics and modeling paradigms for developing and extending enterprise applications.
Integrated Modeling Framework for Enterprise System uses a Meta Model Driven approach to
model engineering. The model captures the business logic and lifecycle semantics of the
component. This approach truly facilitates the "model once run anywhere" paradigm.
The main objective of Integrated Modeling Framework for Enterprise System is to
provide a framework on which models will be generated, resulting in improved design and in
turn improved productivity in an Enterprise. The software industry is trying to fully understand
the modern "Enterprise" in an attempt to automate its day to day operations and to provide
crucial decision support capabilities.
240
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Test Items
FEATURES TO BE TESTED
Following is list of functions that will be tested:
241
Department of Computer Engineering
Vishwakarma Institute of Technology-37
ENVIRONMENTAL NEEDS
The Environmental Needs of the testing phase are the same as specified in the software
requirement specification.
The hardware requirement includes a machine with these minimum requirements.
P3,P4 1.6 GHz or higher
512 MB RAM or higher
Software
Windows operating system XP or higher
Java enabled machine
242
Department of Computer Engineering
Vishwakarma Institute of Technology-37
database
Acknowledgement to user.
profile.
243
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Pass Criteria User must provide valid user name and password.
244
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Fail Criteria If provide incorrect user name and password give error
message.
Pass Criteria User must provide valid user name and password.
245
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Fail Criteria If provide incorrect user name and password give error
message.
db.
246
Department of Computer Engineering
Vishwakarma Institute of Technology-37
error message.
247
Department of Computer Engineering
Vishwakarma Institute of Technology-37
database.
successfully.
db.
248
Department of Computer Engineering
Vishwakarma Institute of Technology-37
249
Department of Computer Engineering
Vishwakarma Institute of Technology-37
database.
data.
250
Department of Computer Engineering
Vishwakarma Institute of Technology-37
database.
requirements.
251
Department of Computer Engineering
Vishwakarma Institute of Technology-37
252
Department of Computer Engineering
Vishwakarma Institute of Technology-37
253
Department of Computer Engineering
Vishwakarma Institute of Technology-37
requirements.
254
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Display notation.
Display acknowledgment.
255
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Display domain.
Display acknowledgment.
256
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Display notations.
Display acknowledgment.
257
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Display transformation.
Display meta-model.
Display model.
Display acknowledgment.
Meta-model missing.
258
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Associate meta-model.
Generate meta-model.
Display meta-model.
Display acknowledgment.
259
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Display acknowledgment.
260
Department of Computer Engineering
Vishwakarma Institute of Technology-37
261
Department of Computer Engineering
Vishwakarma Institute of Technology-37
Verify the domain and get the model as well as verify it.
administrator.
262
Department of Computer Engineering
Vishwakarma Institute of Technology-37
valid.
administrator.
Fail Criteria If provide incorrect user name and password give error
message.
263
Department of Computer Engineering
Vishwakarma Institute of Technology-37
3. TEST PROCEDURE
264
Department of Computer Engineering
Vishwakarma Institute of Technology-37
265
Department of Computer Engineering
Vishwakarma Institute of Technology-37
266
Department of Computer Engineering
Vishwakarma Institute of Technology-37
267
Department of Computer Engineering
Vishwakarma Institute of Technology-37
268
Department of Computer Engineering
Vishwakarma Institute of Technology-37
269
Department of Computer Engineering
Vishwakarma Institute of Technology-37
270
Department of Computer Engineering
Vishwakarma Institute of Technology-37
271
Department of Computer Engineering
Vishwakarma Institute of Technology-37
272
Department of Computer Engineering
Vishwakarma Institute of Technology-37
273
Department of Computer Engineering
Vishwakarma Institute of Technology-37
274
Department of Computer Engineering
Vishwakarma Institute of Technology-37
275
Department of Computer Engineering
Vishwakarma Institute of Technology-37
276
Department of Computer Engineering
Vishwakarma Institute of Technology-37
277
Department of Computer Engineering
Vishwakarma Institute of Technology-37
278
Department of Computer Engineering
Vishwakarma Institute of Technology-37
279
Department of Computer Engineering
Vishwakarma Institute of Technology-37
280
Department of Computer Engineering
Vishwakarma Institute of Technology-37
281
Department of Computer Engineering
Vishwakarma Institute of Technology-37
282
Department of Computer Engineering
Vishwakarma Institute of Technology-37
283
Department of Computer Engineering
Vishwakarma Institute of Technology-37
284
Department of Computer Engineering
Vishwakarma Institute of Technology-37
285
Department of Computer Engineering
Vishwakarma Institute of Technology-37
286
Department of Computer Engineering
Vishwakarma Institute of Technology-37
287
Department of Computer Engineering
Vishwakarma Institute of Technology-37
288
Department of Computer Engineering
Vishwakarma Institute of Technology-37
289
Department of Computer Engineering
Vishwakarma Institute of Technology-37
290
Department of Computer Engineering
Vishwakarma Institute of Technology-37
291
Department of Computer Engineering
Vishwakarma Institute of Technology-37
292
Department of Computer Engineering
Vishwakarma Institute of Technology-37
293
Department of Computer Engineering
Vishwakarma Institute of Technology-37
294
Department of Computer Engineering
Vishwakarma Institute of Technology-37
295
Department of Computer Engineering
Vishwakarma Institute of Technology-37
296
Department of Computer Engineering
Vishwakarma Institute of Technology-37
297
Department of Computer Engineering
Vishwakarma Institute of Technology-37
298
Department of Computer Engineering
Vishwakarma Institute of Technology-37
299
Department of Computer Engineering
Vishwakarma Institute of Technology-37
300
Department of Computer Engineering
Vishwakarma Institute of Technology-37
CONCLUSION
The proposed system aims to address the issues related to all management, planning, and
scheduling, control, and data management functions. Information or data will undergo multiple
transformations i.e. many separate task in fulfilling the information-handling requirements for an
enterprise system. These transformations or tasks are usually successive operations forming sets
of sequential and parallel networks.
Once the integration of all of the informational and customer product and service
functions of an enterprise has been well-planned, the actual implementation of such integration
may be broken into a series of coordinated projects.
All tasks will be defined in a modular fashion, along with their required
interconnections. These tasks will be implemented in a modular fashion, again permitting their
later substitution by other different methods of carrying out the same function.
Apart from this, we have also provided basic modeling and editing tool to simplify the
modeling of UML diagrams namely Usecase diagram, Activity diagram, State chart diagram and
Class diagram etc.
This tool is very useful for efficient and effective Requirement Engineering and Usecase
development especially for enterprise. Because of the simplicity of Integrated modeling
Framework, there is no need to put in extra efforts in learning of this tool.
301
Department of Computer Engineering
Vishwakarma Institute of Technology-37
REFERENCES
302
Department of Computer Engineering