AP4-AA2-EV3-ANÁLISIS E INTERPRETACIÓN DE TEXTOS EN IDIOMA INGLÉS

TECHNOLOGIST ANALYSIS AND DEVELOPMENT OF INFORMATION SYSTEMS (ADSI)

(1565071)

JEINER CLAROS VALDERRAMA

DIEGO VASCO
INSTRUCTOR

LEARNING SERVICE
SENA
2017
Los verbos modales son verbos auxiliares que no pueden funcionar como un verbo
principal, a diferencia de los verbos auxiliares “be”, “do” y “have” que sí pueden funcionar
como un verbo principal.

Los verbos modales expresan modalidad, habilidad, posibilidad, necesidad u otra

condición. Los utilizamos para el futuro y el condicional.

Como verbos complementarios que son, los verbos modales no funcionan sin otro verbo.
Este otro verbo siempre va después del verbo modal y está en la forma base (el infinitivo
sin “to”). No se conjugan los verbos modales y no tienen tiempo.

 can
 could
 may
 might
 will
 shall
 should
 ought to
 must/have to
 would

Usos

Can indica habilidad o posibilidad. En estos casos puede ser traducido como
“poder” en español.

Ejemplos:
I can speak five languages. (Puedo hablar cinco idiomas.)
We can work late tonight if you need us. (Podemos trabajar hasta tarde esta
noche si nos necesitas.)

En frases interrogativas, el uso de “can” puede solicitar permiso o preguntar sobre

posibilidades.
Ejemplos:

Can I have a glass of water? (¿Puedo tomar un vaso de agua?)

Can you help me? (¿Puedes ayudarme?)

Could indica posibilidad o habilidad en el pasado.

Ejemplos:
Joe could speak Spanish when he was young. (Joe podía hablar español cuando era
joven.)
I couldn’t sleep last night. (No pude dormir anoche.)

También se puede usar “could” para posibilidades en el futuro.

Ejemplos:
You could pass the test if you studied. (Podrías pasar el examen si estudiaras.)
I think it could rain later. (Creo que podría llover más tarde.)

Como “can”, en frases interrogativas “could” puede solicitar permiso o preguntar sobre
las posibilidades, pero es más formal.

Could you pass the salt please? (¿Podría pasarme la sal por favor?)
Could you help me? (¿Podrías ayudarme?)

Nota: Se usa “could” en frases condicionales.

May Como “could”, se usa “may” para indicar posibilidades en el futuro.

Ejemplos:
I would bring an umbrella, it may rain later. (Llevaría un paraguas, puede
llover más tarde.)
It may be better to finish this now, rather than wait until tomorrow. (Tal vez sea
mejor terminar esto ahora, en lugar de esperar hasta mañana.)

También se puede utilizar para dar permisos o instrucciones.

Ejemplos:
You may leave if you like. (Puede salir si quiere.)
You may use your cell phones now. (Pueden usar sus teléfonos ahora.)

En frases interrogativas, el uso de “may” es más educado que “can” o “could”.

Ejemplos:
May I have a glass of water? (¿Podría tomar un vaso de agua?)
May I leave now? (¿Podría salir ahora?)

Might Se usa “might” para indicar posibilidades en el presente o el futuro. En estos

casos, es un sinónimo de “may”.

Ejemplos:
I would bring an umbrella, it might rain later. (Yo llevaría un paraguas, puede
llover más tarde.)
It might be better to finish this now, rather than wait until tomorrow. (Tal vez sea
mejor terminar esto ahora, en lugar de esperar hasta mañana.)

También se puede usar al igual que “may”, para pedir permisos o hacer peticiones
corteses, aunque este uso es mucho más común en el Reino Unido que en los Estados
Unidos.

Will Como veremos en lecciones posteriores, se utiliza “will” para formar

el tiempo futuro.

También el uso de “will” significa voluntad o determinación.

Ejemplos:
I will help you. (Te ayudaré.)
We will learn English. (Aprenderemos inglés.)

Se utiliza “will” en frases interrogativas para pedir información, un favor o sobre opciones.

Ejemplos:
Will they find a cure for cancer? (¿Encontrarán una cura para el cáncer?)
Will you help me move? (¿Me ayudas a mudarme?)
 Will he go to Paris by car or train? (¿Irá a París en coche o en tren?)

Shall Se usa “shall” como “will” para formar el tiempo futuro. El uso de “shall”
es mucho más común en el Reino Unido y en general es más educado.

Ejemplos:
Chris shall be happy to see you. (Chris estará feliz de verte.)
I’ll take the 3 o’clock train. (Tomaré el tren a las 15h.)

Nota: Las formas cortas de “will” y “shall” son lo mismo. Entonces “I’ll”en el ejemplo
anterior puede significar “I will” o “I shall”.

También se puede utilizar “shall” para ofertas y sugerencias o para preguntar sobre
opciones o preferencias.

Ejemplos:
Shall we meet at 10pm? (¿Quedamos a las 22h?)
Shall we go to the movies or a museum? (¿Vamos al cine o a un museo?)

Should indica una obligación o recomendación. Refleja una opinión sobre lo que es
correcto. Se traduce como el condicional de “deber” en español.

Ejemplos:
I should call my parents more often. (Debería llamar a mis padres más a
menudo.)
You shouldn’t work so hard. (No debería trabajar tan duro.)
They should practice more if they want to win the championship. (Deberían
practicar más si quieren ganar el campeonato.)

Se utiliza “should” en frases interrogativas para preguntar si existe una obligación o para
pedir una recomendación.
Ejemplos:
Should we leave a tip? (¿Deberíamos dejar una propina?)
Should I have the steak or the chicken? (¿Debería comer el bistec o el pollo?)
Where should they meet you? (¿Dónde deberían encontrarte?)

Ought to es un sinónimo de “should” aunque es menos común.

Ejemplos:
She ought to quit smoking. (Debería dejar de fumar.)
I ought to call my parents more often. (Debería llamar a mis padres más a
menudo.)
They ought to work less. (Deberían trabajar menos.)

Nota: Nunca se usa “ought to” en frases interrogativas en inglés americano .

Must indica una obligación, prohibición o necesidad. También puede

emplearse “have to” (tener que) en frases afirmativas.

Ejemplos:
You must [have to] read this book, it’s fantastic. (Tienes que leer este libro, es
fantástico.)
You must not drink and drive. (No puedes beber y conducir.)
When must we meet you? (¿Cuándo debemos quedar? )

También se puede usar “must” para indicar probabilidad o asumir algo.

Ejemplos:
John’s not here. He must be sick because he never misses class. (John no esta
aquí. Debe estar enfermo porque nunca pierde clases.)
It must be difficult to learn a new language as an adult. (Debe ser difícil aprender
un idioma como adulto.)

Es posible también usar “must” para preguntas retóricas.

Ejemplos:
Must you always be late? (¿Siempre tienes que llegar tarde?)
 Must she talk so much? (¿Tiene que hablar tanto?)

Would Se usa “would” para declarar una preferencia y para preguntar por algo
educadamente.

Ejemplos:
She would like to go to New York someday. (Le gustaría ir a Nueva York
algún día.)
I would like a beer and my wife would like a glass of wine please. (Me
gustaría una cerveza y a mi mujer le gustaría una copa de vino por favor.)
Would you like some coffee? (¿Le gustaría un café?)
Would you help me please? (¿Me ayudas por favor?)
When would you like to go to the movies? (¿Cuándo te gustaría ir al cine?)

Nota: Se usa “would” en frases condicionales.

 MODAL VERBS

characteristics

They act as Express past when Express present or Does not meet the Has no infinitive,
auxiliaries in followed “have + future actions, rule of the "s" for participle, or
sentences. past participle”. when they modify the third person gerund.
a verb in a simple singular.
way.
They are

They are They are They are They are They are

Can - Could May - Might Would Should Must

use use use use use

Indicate When it is Express:

Express physical possibility and followed by an Indicates what Necesidad,
ability and are more formal infinitive verb should be done. deber,
mental ability in their use: without "to" it In its context it obligacion y
forms the translates: deduccion.
Can: May: conditional. Equals:
Puedo, puedes, Acquire the Debe, debes, Debo, debes,
Puedo, puede,
pueden. determination deberían, deben.
pueden.
"ria". deberíamos. To express
Could: Might: obligation in
Podría, podrían. past, future or
Indicate time perfect
possibility must equivalent
to have.
Podia, pude,
pudiste.
 ANALISIS DE SISTEMA
Systems analysis refers to the
process in which analysts go on to
determine how a system should
function.
The analysis should make the
investigations that feasible the
software to be developed.
Analysis involves measurement,
annotation, clarification and
organization.
In SDLC (Systems
Development Life Cycle)
The analysis of systems is the 2
step to follow in the
implementation of a software
system.
DISEÑO DE SISTEMA
 System design tells us how the
system will work.
 The design is already defined to
define how the software will be
made that was feasible for the
company.
 Design involves imagining and
specifying some creation that fits
some requirements.
 In SDLC (Systems Development
Life Cycle) The design of
systems is the third step to
follow in the
implementation of a software
system.
1. that system must use its relational facilities (exclusively) to manage the
database.
2. Specifically, it must support a representation of “missing information and
inapplicable information” that is systematic.
3. It is also implied that such representations must be manipulated by the DBMS
in a systematic way.
4. The system must support an online, inline, relational catalog that is accessible
to authorized users by means of their regular query language.
5. That is, 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.
6. It Can be used both interactively and within application programs.
7. The distribution of portions of the database to various locations should be
invisible to users of the database.
8. This means that data can be retrieved from a relational database in sets
constructed of data from multiple rows and/or multiple tables.
9. This rule states that insert, update, and delete operations should be supported
for any retrievable set rather than just for a single row in a single table.
10. The system must support at least one relational language that.

11. that system have to use its relational facilities (exclusively) to manage the
database.
12. Specifically, it have to support a representation of “missing information and
inapplicable information” that is systematic.
13. It is also implied that such representations have to be manipulated by the
DBMS in a systematic way.
14. The system have to support an online, inline, relational catalog that is
accessible to authorized users by means of their regular query language.
15. That is, users 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.
16. It may be used both interactively and within application programs.
17. The distribution of portions of the database to various locations ought to be
invisible to users of the database.
18. This means that data may be retrieved from a relational database in sets
constructed of data from multiple rows and/or multiple tables.
19. This rule states that insert, update, and delete operations ought to be
supported for any retrievable set rather than just for a single row in a single
table.
20. The system have to support at least one relational language that.

21. that system shall use its relational facilities (exclusively) to manage the
database.
22. Specifically, it shall support a representation of “missing information and
inapplicable information” that is systematic.
23. It is also implied that such representations shall be manipulated by the DBMS
in a systematic way.
24. The system shall support an online, inline, relational catalog that is accessible
to authorized users by means of their regular query language.
25. That is, users shall be able to access the database’s structure (catalog) using the
same query language that they use to access the database’s data.
26. It must be used both interactively and within application programs.
27. The distribution of portions of the database to various locations will be invisible
to users of the database.
28. This means that data must be retrieved from a relational database in sets
constructed of data from multiple rows and/or multiple tables.
29. This rule states that insert, update, and delete operations will be supported for
any retrievable set rather than just for a single row in a single table.
30. The system shall support at least one relational language that.
Systems Analysis: refers to the process in which Analysts go through to determine
how a system should operate - that is determining what functions the system should
perform, whether it’s feasible for the system to be developed (such as financial
feasibility; do the benefits of the system outweigh the costs of developing the
system?), what data is going to be collected and stored.
Systems Design: is actually the third step of the SDLC - it’s where the analysis
designs how the system will operate. The physical components of the system are
defined here which specifies how the problem at hand will be solved.
SDLC: Software Development life cycle,Is the process of creating or modifying the
systems, models and methodologies that people use to develop these software
systems.
Information systems: Is a set of elements oriented to the treatment and
administration of data and information, organized and ready for later use,
generated to cover a need or a goal.
Codd´s rules: Edgar Frank Codd, Was an English computer scientist known
for creating the relational model of databases.
Codd's twelve rules are a set of thirteen rules (numbered zero to twelve) proposed
by Edgar F. Codd, a pioneer of the relational model for databases, designed to
define what is required from a database management system in order for it to be
considered relational, i.e., a relational database management system (RDBMS).
They are sometimes jokingly referred to as "Codd's Twelve Commandments".
relational model for databases: A relational database is a collection of data items
organized into a set of formally described tables from which data can be accessed
or reassembled in many different ways without having to rearrange the tables in
the database.
Primary Key: In designing relational databases, the primary key is called a field or
a combination of fields that uniquely identifies each row in a table. A primary key
thus comprises a column or set of columns. There can not be two rows in a table
that have the same primary key.
Null values: A null value is an indicator that tells the user that the data is missing
or not applicable. For convenience it is said that the missing data has the value
NULL. The NULL value is not a real numeric data. Instead, it is a signal or a
reminder that the data value is missing or unknown. In the SQL database language
there is a set of special rules that govern the handling of NULL values.
DBMS: data base management system is a set of programs that allow the storage,
modification and extraction of information in a database, as well as providing tools
to add, delete, modify and analyze data. Users can access the information using
specific query and report generation tools, or through applications to that effect.
programming language: A programming language is a formal language designed
to perform processes that can be carried out by machines such as computers. They
can be used to create programs that control the physical and logical behavior of a
machine, to express algorithms with precision, or as a mode of human
communication.
Rollback: a rollback or rollback is an operation that returns the database to some
previous state. Rollbacks are important for database integrity, because they mean
that the database can be restored to a clean copy even after erroneous operations
have been performed. They are crucial for recovering crashes from a database
server; By performing a rollback of any transaction that was active at the time of
the crash, the database is restored to a consistent state.
Commit: Refers to the idea of recording a set of "tentative" changes permanently.
A popular usage is at the end of a database transaction.
Arrays: An array is a means of storing a set of objects of the same class. Each
individual element of the array is accessed by an integer called the index. 0 is the
index of the first element and n-1 is the index of the last element, where n is the
dimension of the array.
interface: In computing, it is used to name the functional connection between two
systems, programs, devices or components of any type, which provides a
communication of different levels allowing the exchange of information.
Workflow: Essential art of software for collaborative work (groupware) is precisely
the workflow. A workflow application automates the sequence of actions, activities
or tasks used to execute the process, including tracking the status of each of its
stages and providing the necessary tools to manage it.
SAD: Is a system that helps decision making, technology and management,
facilitating the organization of knowledge in poorly structured, semi-structured or
unstructured topics.
Flowchart: In Unified Modeling Language (UML), it is an activity diagram
that represents the step-by-step business and operational workflows of the
components in a system. An activity diagram shows the general control flow.
Software: Hardware or software of a computer system comprising all the
necessary logical components which make it possible to carry out specific tasks.
Hardware: In computing refers to the tangible physical parts of a computer
system; Its electrical, electronic, electromechanical and mechanical components.1
Cables, cabinets or boxes, peripherals of all kinds and any other physical element
involved make up the hardware.
Modals verbs: Modal verbs are auxiliary verbs that can not function as a main
verb, as opposed to the auxiliary verbs "be", "do" and "have" that can function as a
main verb.
Modal verbs express modality, ability, possibility, necessity or other condition. We
use them for the future and the conditional.
As complementary verbs that are, the modal verbs do not work without another
verb. This other verb always goes after the modal verb and is in the base form (the
infinitive without "to"). Modal verbs are not conjugated and do not have time.
https://es.wikipedia.org/wiki/Sistema_de_informaci%C3%B3n
https://es.wikipedia.org/wiki/Systems_Development_Life_Cycle
https://es.wikipedia.org/wiki/Edgar_Frank_Codd
https://en.wikipedia.org/wiki/Codd%27s_12_rules
http://searchdatacenter.techtarget.com/es/definicion/Base-de-datos-relacional
https://es.wikipedia.org/wiki/Clave_primaria
https://www.codejobs.biz/es/blog/2014/07/02/los-valores-null-bases-de-datos
https://es.wikipedia.org/wiki/Sistema_de_gesti%C3%B3n_de_bases_de_datos
https://www.mastermagazine.info/termino/4544.php
https://es.wikipedia.org/wiki/Lenguaje_de_programaci%C3%B3n
https://es.wikipedia.org/wiki/Rollback
https://es.wikipedia.org/wiki/Commit
http://www.sc.ehu.es/sbweb/fisica/cursoJava/fundamentos/clases1/arays.htm
https://es.wikipedia.org/wiki/Interfaz
https://es.wikipedia.org/wiki/Flujo_de_trabajo