Table Of Content*0
>
NPS CS-92-020
NAVAL POSTGRADUATE SCHOOL
Monterey, California
A
Design Management and Job
Assignment System
Salah M. Badr
Valdis Berzins
Approved for public release; distribution is unlimited.
Prepared for:
Naval Postgraduate School
Monterey, California 93943
FedDocs
D 208.1M/2
NPS-CS-92-020
NAVAL POSTGRADUATE SCHOOL
Monterey, California
REAR ADMIRAL R. W. WEST JR.. HARRISON SHULL
Superintendent Provost
This report was prepared for and funded by the Naval Postgraduate School.
Reproduction ofall orpart ofthis report is authorized.
This report was prepared by:
DUDLEYKNOX LIBRARY
CURITYCLASSIFICATIONOFTHISPAGE t.AWM pnRTftRADUATE SCHOOL
REPORT DOCUMENTATION PAGE MONTEREY CA 93943*1ui
a. REPORT SECURITY CLASSIFICATION UNCLASSIFIED 1b. RESTRICTIVE MARKINGS
!a SECURITY CLASSIFICATIONAUTHORITY 3. DISTRIBUTION/AVAILABILITYOP REPORT
Approved for public release;
!b. dECLASSIFICATIONVdOWNgRAdINgSCHEDULE distribution is unlimited
i. PERFORMINGORGANIZATION REPORT NUMBER(S) s. MONITORSorganisation REPORTNumBER(S)
nIPS CS-92-020
a.NAMEOP ERFORMINgORGANIZATION 6b OFFICE SYMBOL 7a. NAME OF MONITORINGORGANIZATION
Computer cience Dept. (ifapplicable) Naval Postgraduate School
cs
vJaval Postgraduate School
>c.ADDRESS(City, State, andZIPCode) 7b. ADDRESS(City, State, andZIPCode)
Monterey, CA 93943-5000
Monterey, CA 93943-5000
la.ONRAGMAENIOZPATFIUONNDING/SPONSORING 8b O(PitPaIpCplEicSabYlMe)BOL 9. PROCUREMENT INSTRUMENT IDENTIFICATION NUMBER
NJaval Postgraduate School
MJco.nAtDeDrReEyS,SC(CiAty, Stat9e,3a9n4d3Z-IP50Co0d0e) EP10LREOSMGOERUNARTMCNEO.OP FUNPNORD.OIJNEGCNTUMBERS TNOA.SK AWCOCREKSSUINOITN NO.
11.TITLE (IncludeSecurityClassification)
A Design Management and Job Assignment System
PERSONALAUTHOR(S)
J2. SALAH M. BADR, VALDIS BERZINS'
i$a.TYPEOFREPORT isb. TIME COVERED 14. DATE OF REPORT(Year, Month, Day) 15. PASE COUNT
Techinical from 05/89 to 03/90 December 1992 25
16. SUPPLEMENTARY NOTATION
17. COSATI CODES 18.SSOUFBJTEWCTATREERMESV(COonLtiUnuTeIonOrNev,erJseOifBneAceSssSarIyGaNndMidEenNtiTfy,byDblEocSkInuGmNberD)ATABASE,
FIELD GROUP SUB-GROUP
EVOLUTION STEP, SOFTWARE PROTOTYPING.
19.ABSTRACT(Continueonreverseifnecessaryandidentifybyblocknumber)
This report introduces the basic approach taken in designing the design
management and job assignment system (DMJAS)for CAPS93. This approach uses a
model of software evolution [8] which defines how a software change, once has
been approved, will be applied to the software release (version) to produce
another version of the software incorporating this change. This process is
called an evolution step. The proposed system represents a management layer
between the user interface (supporting two user classes, managers and design-
ers) and the design database. The DMJAS controls the software evolution pro-
cess in an incrementally evolving software system where The job steps to be
scheduled are only partially known: time required, the set of sub-tasks for
each step, and the input/output constraints between steps are all uncertain,
and are all subject to change as steps are carried out. Models of design data-
base and manager/designer interface are explained followed by the proposed
system.
SoQDIUSNTCRLIABSUSTIIFOINE/DA/VUANILLIAMBIILTIETDYOQPASB5ATMREAACS1RPT. Q DTIC USERS 21U.NACBSLTARSACSTISFEICUERDITY CLASSIFICATION
WOJ^iM2MLEIND,VIDUAL 22b. TELEPHONE/7nc/ude>4«?aCode) 22C.OFFICE SYMBOL
(408) 656-2903
)DFORM 1473,84 MAR 83APRedition maybe useduntil exhausted SECURITY CLASSIFICATION OFTHIS PAGE
Allothereditionsareobsolete UNCLASSIFIED
A
Design Management and Job Assignment
System1
Salah Badr
Valdis Berzins
Naval Postgraduate School
Department of Computer Science
Monterey, California 93943-5100 USA
ABSTRACT
This report introduces the basic approach taken in
designing the design management and job assignment system
(DMJAS) for CAPS93. This approach uses a model of software
evolution [8] which defines how a software change, once has
been approved, will be applied to the software release (ver-
sion) to produce another version of the software incorporat-
ing this change. This process is called an evolution step.
The proposed system represents a management layer between
the user interface (supporting two user classes, managers
and designers) and the design database. The DMJAS controls
the software evolution process in an incrementally evolving
software system where The job steps to be scheduled are only
partially known: time required, the set of sub-tasks for
each step, and the input/output constraints between steps
are all uncertain, and are all subject to change as steps are
carried out. Models of design database and manager/designer
interface are explained followed by the proposed system.
KEYWORDS
SOFTWARE EVOLUTION, JOB ASSIGNMENT, DESIGN DATABASE,
EVOLUTION STEP, SOFTWARE PROTOTYPING,SOFTWARE ENGINEERING.
1. Introduction
"The Computer Aided Prototyping System (CAPS) an inte-
,
grated set of computer aided software tools, has been
1. Thisresearch was supported in partby theArmyResearch Office undergrantnumberARO-145-91
ADesignManagementandJobAssignmentSystem January 13, 1993
designed to support prototyping of complex software systems.
CAPS can increase the leverage of the prototyping strategy
by reducing the effort of the designer puts into producing
and adapting a prototype to perceived user needs." [7]
In the context of the CAPS system, there are three main
entities that interact to develop a software system. These
main entities are the project manager, the CAPS system, and
the software designers. Currently CAPJ92 has only two of these
main entities: the designer and CAPS system. The designer can
select a tool, then select a prototype to work with. The
designer can commit his work to the design database whenever
he wants. When a designer is modifying a prototype no other
designer can access the same prototype for modification. Cur-
rently CAPS does not have any mechanisms for coordinating
parallel efforts by different designers. This paper presents
the design of such a mechanism for C^PS93.
The inter-relation between these three main entities in
CAPS93 is depicted in figures 1, 2, and 3 The project manager
.
should be able to enter/edit description of top level evolu-
tion steps. An evolution step has many properties and
operations such as base version, change description, primary
input, initial conditions, commit, abandon/suspend, and any
optional data such as priority, or deadlines. The manager
ADesignManagementandJobAssignmentSystem January 13, 1993 2
.
should be able to monitor and control all the activities of
the development team through making all the control informa-
tion accessible to him such as the incremental task schedule
describing who is supposed to do what and when. The Manager
can act as a designer and can be assigned some development
tasks
r
Manager
Base Version
Change List Change description
Suspend List Primary input
Incremental Sch. Initial Conditions
Assign Task Commit
Abandon/Suspend
Optional data.
FIGURE 1 The DMJAS Manager Interface
.
The designer interface with the DMJA system is simplified
to keep the designer's attention on doing the tasks assigned
to him. This interface can assign tasks from the system to the
designer and gets back his commit response. Designers can work
on parallel on different tasks related to the same software
ADesignManagementandJobAssignmentSystem January 13, 1993
version, or on the same task splitting different variations
(alternatives)
.
Commit
Suspend
Assign Task
Release
Release Task
FIGURE 2 DMJAS Designer Interface
.
Version control and design management are also part of our
contribution as tasks of the DMJA system as well as preserving
data consistency through propagating change consequences. In
section 2 some concepts used in the database schema for our
work are defined. A comparison to the previous work is pre-
sented in section 3. In section 4 the underlying design
database is defined. Sections 5 and 6 introduce both the
designer and manager interfaces. The CMJA system is presented
in section 7. Finally conclusions and suggestions for future
work are presented in section 8.
ADesignManagementandJobAssignmentSystem January 13, 1993
2. Definitions
Since the DMJAS is a management layer on top of the
design database, it gets most of its input data and sends
most of its output data from/to the design database. It logs
the evolution steps with their relevant information to the
history log, assigns variation and version numbers to the
new versions resulting from applying the evolution steps,
queries the design database for the decomposition as well as
the dependency relations between different objects, copies
the tasks to be modified to the assigned designer's work
area, and controls commitment of completed modifications to
the database. The underlying database schema for our work
includes the following concepts [8]:
An object is a software component that is subject to
change. Objects can be either composite or atomic. Objects
can be changed only by creating new versions. Object is a
generalized type with many specialized subtypes that can
include requirements, specifications, designs, code, test
cases, etc.
A version is an immutable snapshot of an object. Versions
have unique identifiers. New versions can be created, but
versions cannot be modified after they are created.
ADesignManagementandJobAssignmentSystem January 13, 1993
A variation of an object is a totally ordered sequence of
versions of the object which represent the evolution his-
tory of an independent line of development.
An evolution step represents the activity of creating a new
version of the source description of a software object.
Evolution steps usually require creativity and human
effort from the manager responsible for the step.
A software component or step is composite if it can be
viewed as a collection of related parts, and is atomic oth-
erwise.
A top level Evolution Step represents the activity of ini-
tiating, analyzing, and implementing a change request in
the system.
X uses Y: a relationship that is true if and only if the
semantics or implementation of one software object X
depends on another software object Y [4],
X used-by Y: same as Y uses X.
3. Previous Work
According to [11] representations of the versioning pro-
cess can be classified into two main models. The first model
is the conventional Version Oriented Model VOM in which a
ADesignManagementandJobAssignmentSystem January 13, 1993
