Inicio de la semana i! Identidad digital.

Identidad digital: Que es la identidad digital? Este termino lleva resonando últimamente en nuestra sociedad. Con la evolución de la tecnología.

La identidad digital no solo es nuestro nombre. Tenemos que irnos mas adentro, esto refleja nuestra identidad y de acuerdo a la definición de identidad son el conjunto de rasgos que nos definen y dicen quienes somos.

Eso es la identidad digital, como somos, gustos,rasgos y esencia de nuestra persona en Internet.

Yo vengo de una familia no muy tecnológica y muy conservadora. de chico no me dejaban registrarme ni dar información de verdad.

Mi primer contacto con mi identidad digital fue mi amor a los video juegos que me llevaron a crear un personaje y quien soy en linea, con quien loger conseguir demasiados amigos en linea.

es algo de verdad y algo muy grande.

Palabras que me describen.

Positive.- I considere myself a person who is always looking the good part of the world, always trying to get the moral up of the persons around me.

Fleixible.- Cause i can adapt to a lot of situations and try to give the best of me.

Love.- Iam the kind of person that thinks that giving love to the world is the answer to everything.

Loyalty.- I now that iam no the greatest to be a leader but iam one of the most loyl person to my friends.

Persistent.- Iam a try hard in a competitive way, iam always trying to do the best.

User interface design

The user interface design is the design of computers, machines, mobile devices, software applications, and websites focused on user experience and interaction. Usually it is a multidisciplinary activity involving different branches such as: graphic design, industrial, web, software and ergonomics. Its objective is to make applications or objects more attractive and also assure that the user interaction is as intuitive as possible, known as user-centered design.

Unified Modeling Language

The Unified Modeling Language (UML) is a general-purpose, developmental, modeling language in the field of software engineering, that is intended to provide a standard way to visualize the design of a system.

UML was originally motivated by the desire to standardize the disparate notational systems and approaches to software design developed by Grady Booch, Ivar Jacobson and James Rumbaugh at Rational Software in 1994–95, with further development led by them through 1996.

In 1997 UML was adopted as a standard by the Object Management Group (OMG), and has been managed by this organization ever since. In 2005 UML was also published by the International Organization for Standardization (ISO) as an approved ISO standard. Since then it has been periodically revised to cover the latest revision of UML.

Though well-known and widely used in education and academic papers, as of 2013 UML is little-used in industry, and most such use is informal and ad hoc.

What is software architecture?

example:

Software application architecture is the process of defining a structured solution that meets all of the technical and operational requirements, while optimizing common quality attributes such as performance, security, and manageability. It involves a series of decisions based on a wide range of factors, and each of these decisions can have considerable impact on the quality, performance, maintainability, and overall success of the application.

Like any other complex structure, software must be built on a solid foundation. Failing to consider key scenarios, failing to design for common problems, or failing to appreciate the long term consequences of key decisions can put your application at risk. Modern tools and platforms help to simplify the task of building applications, but they do not replace the need to design your application carefully, based on your specific scenarios and requirements. The risks exposed by poor architecture include software that is unstable, is unable to support existing or future business requirements, or is difficult to deploy or manage in a production environment.

Software life-cycle

It describes the development of software, from the beginning to end. Its purpose is to define the intermediate phases in order to validate the application development. Thus, to ensure that the software meets the requirements for the implementation and verification of development procedures: it ensures that the methods used are appropriate.

This programs are implemented due to the fact that it is very expensive to fix an error that are identified in the late implementation phase. The software life-cycle helps to identify the errors as soon as possible; this helps the developers, so they can focus on quality of the software.

Waterfall model

The waterfall model is a popular version of the systems development life cycle model for software engineering. Often considered the classic approach to the systems development life cycle, the waterfall model describes a development method that is linear and sequential.

The advantage of waterfall development is that it allows for departmentalization and managerial control.

The disadvantage of waterfall development is that it does not allow for much reflection or revision. Once an application is in the testing stage, it is very difficult to go back and change something that was not well-thought out in the concept stage.

The Waterfall method makes the assumption that all requirements can be gathered up front during the Requirements phase (Kee, 2006). Communication with the user is front-loaded into this phase, as the Project Manager does his or her best to get a detailed understanding of the user’s requirements. Once this stage is complete, the process runs “downhill” (Hoffer, et al, 2008).

The Design phase is best described by breaking it up into Logical Design and Physical Design subphases. During the Logical Design phase, the system’s analysts makes use of the information collected in the Requirements phase to design the system independently of any hardware or software system (Hoffer, et al, 2008). Once the higher-level Logical Design is complete, the systems analyst then begins transforming it into a Physical Design dependent on the specifications of specific hardware and software technologies (“Software Development Lifecycle”, n.d.)

Sofware life-cycle

Is the methodological approach ordering rigorously stages of software development, so that the start of each stage must wait for the completion of the before. At the end of each stage, the model is designed to carry conduct a final review, which is responsible for determining whether the project is ready to move to the next phase. This model was the first to originate and is the basis of all other life cycle models.

History of software engineering

From its beginnings in the 1960s, writing software has evolved into a profession concerned with how best to maximize the quality of software and of how to create it.

How best to create high quality software is a separate and controversial problem covering software design principles, so-called “best practices” for writing code, as well as broader management issues such as optimal team size, process, how best to deliver software on time and as quickly as possible, work-place “culture”, hiring practices, and so forth. All this falls under the broad rubric of software engineering.

You’ve probably heard of the first widely used programming language — IBM’s Fortran — which was released in 1957 for mathematical and scientific computing. Another, Cobol, was released by the US Department of Defense in 1962 for use in business applications.

Over the following decades, the discipline of programming saw a familiar tension between the scientific thinking of academia, which tended to seek idealized solutions to engineering challenges, and the practical needs of an industry faced with real-life time and cost pressures (and bloated code bases). The early 70’s saw the emergence of key ideas in systems thinking which allowed engineers to break these giant projects into modular (and much more manageable) pieces that communicated via interfaces.

Data and MetaData

What is data??

is a set of values of qualitative or quantitative variables.

Pieces of data are individual pieces of information. While the concept of data is commonly associated with scientific research, data is collected by a huge range of organizations and institutions, ranging from businesses.

The first English use of the word “data” is from the 1640s. “Data” is the “…plural of datum, from Latin datum “(thing) given,” neuter past participle of dare “to give”. Using the word “data” to mean “transmittable and storable computer information” was first done in 1946. The expression “data processing” was first used in 1954.

Data is measured, collected and reported, and analyzed, whereupon it can be visualized using graphs, images or other analysis tools. Data as a general concept refers to the fact that some existing information or knowledge is represented or coded in some form suitable for better usage or processing. Raw data (“unprocessed data”) is a collection of numbers or characters before it has been “cleaned” and corrected by researchers. Raw data needs to be corrected to remove outliers or obvious instrument or data entry errors (e.g., a thermometer reading from an outdoor Arctic location recording a tropical temperature). Data processing commonly occurs by stages, and the “processed data” from one stage may be considered the “raw data” of the next stage.

What is meta data?

Metadata are “data [information] that provide information about other data”. Two types of metadata exist: structural metadata anddescriptive metadata. Structural metadata are data about the containers of data. Descriptive metadata use individual instances of application data or the data content. Metadata were traditionally used in the card catalogs of libraries until the 1980s, when libraries converted their catalog data to digital databases.

as digital formats are becoming the prevalent way of storing

Continue reading →