20 may 2016

Definición de requerimiento de software


  • Los requerimientos son especificaciones de lo que debe ser implementado en un sistema. Son descripciones de cómo debe comportarse un sistema, sus características o atributos.
  • Un requerimiento es una necesidad documentada sobre el contenido, forma o funcionalidad de un producto o servicio.
  • Los requerimientos son declaraciones que identifican atributos, capacidades, características y cualidades que necesita cumplir un sistema para que tenga valor y utilidad para el usuario. En otras palabras, los requerimientos muestran qué elementos y funciones son necesarias para un sistema.
  • Los requerimientos, son una condición o necesidad de un usuario para resolver un problema o alcanzar un objetivo. 
  • Se deberá entender como requerimiento cualquier acción, característica, necesidad o regla de negocio que tenga relevancia para la creación de un sistema. Dependiendo de su complejidad o reusabilidad, estos requerimientos pueden ser organizados de forma jerárquica e integrar paquetes que permitan agrupar dichos requerimientos en conjuntos que hagan sentido a la operación como módulos o sistemas.

16 may 2016

Some definitions of requirements



Requirement is anything that drives design choices (Brian Lawrence) ...

Requirements are a specification of what should be implemented. They are descriptions of how the system should behave, or of a system property or attribute. They may be a constraint on the development process of the system...





8 abr 2016

Why do I need an enterprise architecture?

http://www.opengroup.org/

The purpose of enterprise architecture is to optimize across the enterprise the often fragmented legacy of processes (both manual and automated) into an integrated environment that is responsive to change and supportive of the delivery of the business strategy.

Today’s CEOs know that the effective management and exploitation of information through IT is a key factor to business success, and an indispensable means to achieving competitive advantage. An enterprise architecture addresses this need, by providing a strategic context for the evolution of the IT system in response to the constantly changing needs of the business environment.

Furthermore, a good enterprise architecture enables you to achieve the right balance between IT efficiency and business innovation. It allows individual business units to innovate safely in their pursuit of competitive advantage. At the same time, it ensures the needs of the organization for an integrated IT strategy are met, permitting the closest possible synergy across the extended enterprise.

The advantages that result from a good enterprise architecture bring important business benefits, which are clearly visible in the net profit or loss of a company or organization:

A more efficient business operation:
  • Lower business operation costs
  • More agile organization
  • Business capabilities shared across the organization
  • Lower change management costs
  • More flexible workforce
  • Improved business productivity
 A more efficient IT operation:
  • Lower software development, support, and maintenance costs
  • Increased portability of applications
  • Improved interoperability and easier system and network management
  • Improved ability to address critical enterprise-wide issues like security
  • Easier upgrade and exchange of system components
Better return on existing investment, reduced risk for future investment:
  • Reduced complexity in the business and IT
  • Maximum return on investment in existing business and IT infrastructure
  • The flexibility to make, buy, or out-source business and IT solutions
  • Reduced risk overall in new investments and their cost of ownership
Faster,simpler,and cheaper procurement:
  • Buying decisions are simpler, because the information governing procurement is readily available in a coherent plan
  • The procurement process is faster — maximizing procurement speed and flexibility without sacrificing architectural coherence
  • The ability to procure heterogeneous,multi-vendor open systems
  • The ability to secure more economic capabilities
http://www.opengroup.org/


4 ene 2016

Diagrama del proceso básico de recuperación de contraseña

Les comparto un diagrama del proceso básico de recuperación de contraseña. No sigue las reglas al 100% de la notación BPMN.


23 dic 2015

Diagrama del proceso básico de autenticación contra base de datos

Les comparto un diagrama del proceso básico de autenticación / autorización contra bases de datos. No sigue las reglas al 100% de la notación BPMN.