Laboratorio modelo relacional base de datos 18/03/2018

Colegio Alemán de Cali Pág. 1 de 5

AP3-AA1-Ev4-Construcción de Diagramas UML del proyecto de formación

JOHN DEIBY QUINTERO RESTREPO

LUIS GABRIEL CUBILLOS HOYOS

YESID FERNANDO ESPAÑA

INSTRUCTORES:

DIANA MARIA RICO

LUIS CARLOS OSSA GOMEZ

SERVICIO NACIONAL DE APRENDIZAJE

ANALISIS Y DESARROLLO DE SISTEMAS DE INFORMACIÓN

REGIONAL ANTIOQUÍA

2017

Recepción de Solicitudes Tecnológicas

Marco de Referencia de Desarrollo de Software

 Laboratorio modelo relacional base de datos 18/03/2018
Colegio Alemán de Cali Pág. 2 de 5

Análisis e interpretación de textos en idioma inglés

1. CONCEPTUAL MAP

2. COMPARATIVE TABLE

SYSTEM ANALYSIS VERSUS SYSTEM DESIGN

SYSTEM ANALYSIS AND SYSTEM DESING

ANALYSIS DESING
How How a system should operate How the system will operate
What What functions the system should perform Define the physical components
Creation SIMILARITIES
Recepción de Solicitudes Tecnológicas

Marco de Referencia de Desarrollo de Software

 Laboratorio modelo relacional base de datos 18/03/2018
Colegio Alemán de Cali Pág. 3 de 5

Process
1. You will have to conduct preliminary researches.
2. You would choose to buy an off the shelf application or customize a software
application catering to their specific needs.
3. Present your final proposal to your client
4. You will implement your solution and train the employees on the new
system.
DIFFERENCES

ANALYSIS DESING
It involves measuring. It involves imagining.
It implicates Clarifying, Organizing and It involves specifying some
In Software itemizing. creation
Development You can only validate an analysis as right It needs fits some requirements.
or wrong, never good or bad. You can judge a design as good or
bad.
Analysis is typically performed in Design is performed when the
preparation for some other activity. decision is made to build
something

3. TEN SENTENCES WITH MODAL VERBS IN “CODD´S” DOCUMENT

 The system must qualify as relational, as a database, and as a management system.

 It can be used both interactively and within application programs.
 All data must be accessible
 The DBMS must allow each field to remain null.
 The distribution of portions of the database to various locations should be invisible to users of the
database.
 Users must be able to access the database’s structure (catalog) using the same query language that
they use to access the database’s data.
 The system must support set-at-a-time insert, update, and delete operators.
 Integrity constraints must be specified separately from application programs and stored in the catalog.
 It must be possible to change such constraints as and when appropriate without unnecessarily
affecting existing applications.
 Existing applications should continue to operate successfully
4. TEN CORRECT VARIATIONS IN SENTENCES USING MODAL VERBS

 The system should / have to qualify as relational, as a database, and as a

management system.
 It may be used both interactively and within application programs.
 All data should /have to be accessible
Recepción de Solicitudes Tecnológicas

Marco de Referencia de Desarrollo de Software

 Laboratorio modelo relacional base de datos 18/03/2018
Colegio Alemán de Cali Pág. 4 de 5

 The DBMS should /have to allow each field to remain null.

 The distribution of portions of the database to various locations ought to be invisible to users of the
database.
 Users should /have to be able to access the database’s structure (catalog) using the same query
language that they use to access the database’s data.
 The system should / have to support set-at-a-time insert, update, and delete operators.
 Integrity constraints should /have to be specified separately from application programs and stored in
the catalog.
 It should /have to be possible to change such constraints as and when appropriate without
unnecessarily affecting existing applications.
 Existing applications ought to continue to operate successfully

5. TEN WRONG VARIATIONS IN LAST SENTENCES USING MODAL VERBS

 The system can qualify as relational, as a database, and as a management system.

 It must be used both interactively and within application programs.
 All data can be accessible
 The DBMS can allow each field to remain null.
 The distribution of portions of the database to various locations could be invisible to users of the
database.
 Users can be able to access the database’s structure (catalog) using the same query language that
they use to access the database’s data.
 The system can support set-at-a-time insert, update, and delete operators.
 Integrity constraints can be specified separately from application programs and stored in the catalog.
 It can be possible to change such constraints as and when appropriate without unnecessarily affecting
existing applications.
 Existing applications could continue to operate successfully.

GLOSARY

REQUIRES: Requiere
DEVELOPING: Desarrollo
CONTINGENCIES: Contingencias
STATEMENT : Declaración
FINANCIAL: Fiscal
FEASIBILITY: Viabilidad
ROW: Fila
CURRENT: Actual
Recepción de Solicitudes Tecnológicas

Marco de Referencia de Desarrollo de Software

 Laboratorio modelo relacional base de datos 18/03/2018
Colegio Alemán de Cali Pág. 5 de 5

FLOW: Flujo
MANAGEMENT: Gestión
TOOLS: Herramientas
PERFORMED: Realizado
DATABASES: Bases De Datos
CAMPAIGN: Campaña
QUALIFY: Calificar
REQUIREMENT: Requisito
SYSTEMATIC: Sistemática
SUPPORT: Apoyo
INTERACTIVELY: Interactivamente
OPERATIONS: Operaciones

Recepción de Solicitudes Tecnológicas

Marco de Referencia de Desarrollo de Software