PERFIL DEL ANALISTA DE SISTEMAS

Proactive, fast learner and team player. Knowledge of the following technologies:VB.NET, C#, ASP.NET, Visual Studio.NET (2003-2005), SQL Server 2000, and Visual Basic 6.0
SAP, JDEdwards, MAPICS u otros sistemas de igual alcance.
PowerMHS

ANALISTA DE SISTEMAS

a. Responsable de recoger todos los requerimientos del negocio, esos requerimientos llevarlos a un diseño funcional y validar que la solución provista cumple con los requisitos del negocio.
b. Realiza reuniones con los usuarios para recoger los requerimientos de la solución.
c. Analiza, resume y documenta la información obtenida
d. Participa en la definición del proyecto
e. Convierte los requerimientos funcionales en requerimientos técnicos que serán utilizados por el equipo de desarrollo.
f. Realiza reuniones con los usuarios para validar la solución presentada
g. Trabaja con el Gerente de Calidad para desarrollar un plan de prueba para los sistemas.
h. Revisa, analiza y evalúa los sistemas actuales y las necesidades de los usuarios.
i. Documenta detalladamente las especificaciones del proyecto como los requerimientos del negocio y programas.
j. Documenta detalladamente los pasos requeridos para desarrollar o modificar los sistemas.
k. Redacta en detalle posibles escenarios de la solución
l. Contribuye y es responsable de continuar con la documentación estandarizada y los SOP.
m. Es la persona que sirve de enlace entre el usuario y el programador.
n. Decide cómo se realizará o se diseñará un sistema, cómo se implementará un paquete nuevo y cómo se ajusta a PowerMHS (interfaces, etc.)
o. Reuniones con todos los usurarios, con socios de negocio y suplidores, lecturas de manuales y/o regulaciones.


Bachillerato en Sistemas de Información o Ciencias en Computadora. Experiencia en implementación de soluciones tecnológicas (programas, aplicaciones, etc.) De 4-5 años de experiencia. Debe ser un facilitador y tener actitud de innovar. Bilingue.

Business Objects, SQL 2000, Crystal Reports, MS Excel and SAS (or similar software) proficiency
XLM, J2EE, Front Page and HTML
MS SQL, MS Reporting Services, Business Intelligence, MS.NET, C#, ASP.NET, MS Sharepoint.
AS/400 operation

Active Information Systems student coursing a major in NETWORKING and PROGRAMMING. Proactive, fast learner, team player, disciplined and computer entusiast.
Amdocs Ensemble point to point, APIs, Weblogic, ESB, Java Bean and JAVA
(.Net 3.0+, C#, T-SQL, Visual Studio 2005/2008)

• Experience with SOAP, XML, XSL, XSLT

PASOS DEL PLAN PRELIMINAR

PLANIFICACION (INVESTIGACION PRELIMINAR)

Paso I ENTENDER el problema u oportunidad (DA UNA DEFINICION)
¿Quiénes están envueltos?
- Departamentos
- Usuarios
- Procesos

Paso 2 DEFINIR el alcance y restricciones
- Alcance (Scope)

Paso 3 RECOLECTAR Información
- Analizar gráficas y diagramas
- Entrevistas
- Revisar Documentación
- Observar operaciones
- Inyectar cuestionarios
 
Paso 4 EVALUAR VIABILIDAD
- Operacional
- Técnica
- Económica
- Tiempo

Paso 5 ESTIMAR Costos y Tiempo de Desarrollo
- ¿Qué información quieres recolectar?
- ¿Cómo vas a manejar esa información?
- ¿Cuáles son tus fuentes de datos?
- ¿Qué dificultades encuentras en la recolección de datos?
- ¿Quién realizará la entrevista?
- ¿A cuantas personas se entrevistará?
- ¿Con cuanto tiempo cuentas para realizar las entrevistas?
- ¿Tiempo para resumir hallazgos?
- ¿Cuánto costará analizar esa data y presentar reportes e informes con hallazgos y recomendaciones?

Paso 6 PRESENTAR RESULTADOS Y RECOMENDACIONES A GERENCIALES
- Reportes (Gann Chart)
- Recordar que el formato varía de compañía a compañía.
o FORMATO:
 Introducción
 Resumen de Requerimientos del Sistema
 Hallazgos
 Recomendaciones
 Estimados en Tiempo y Costo
 Beneficios esperados
 Apéndices

ESTUDIO DE COSTOS

COSTOS
Types of Costs Examples
Procurement Consulting costs
Equipment purchase or lease
Equipment installation costs
Site preparation and modifications
Capital costs
Management and staff time
Start-Up Operating system software
Communications equipment installation
Start-up personnel
Personnel searches and hiring activities.
Disruption to the rest of the organization.
Management to direct start-up activity.
Project-related Application software
Software modifications to fit local systems.
Personnel, overhead, et al, from in-house development.
Training users in application use
Collecting and analyzing data
Preparing documentation
Managing development
Operating System maintenance costs (hardware, software and facilities)
Rental of space and equipment.
Asset depreciation.
Management, operation, and planning personnel.

RECURRING COSTS
- Application software maintenance
- Incremental data storage expense
- Incremental communications.
- New software and hardware leases.
- Supplies and other expenses (for example, paper, forms, data center personnel).

ONE-TIME COSTS
- Development costs
- New Hardware
- New (purchased) software, if any
o Packaged applications software
- User training
- Site preparation

BENEFICIOS TANGIBLES E INTANGIBLES

BENEFICIOS TANGIBLES
A. Cost Reduction or Avoidance
B. Error Reduction
C. Increased Flexibility
D. Increased Speed of Activity
E. Improvement in management planning or control
F. Other
BENEFICIOS INTANGIBLES
- Competitive necessity
- More timely information
- Improved organizational planning
- Increased organizational flexibility
- Promotion of organizational learning and understanding
- Availability of new, better, or more information.
- Ability to investigate more alternatives.
- Faster decision making
- Information processing efficiency.
- Improved asset utilization.
- Improved resource control.
- Increased accuracy in clerical operations.
- Improved work process that can improve employee morale.
- Positive impacts on society.

DCA

DCA

- Si fuera necesario, se dará la formación adecuada al moderador y el escribiente de la sesión.
- Se distribuirá entre los participantes adecuados la agenda de la misma y la documentación anteriormente reunida.
- Se programará el lugar donde se llevará a cabo la sesión.
- Se desarrollará un guión que deberá seguirse durante la sesión DCA (ampliación de la del moderador)
- Se prepararán soportes de transparencias u otros medios de exposición con apoyo de equipos audiovisuales.
- NO desviarse excesivamente de la agenda propuesta.
- Vigilar la programación (Asignar tiempo a cada punto)
- Asegurar que el escribiente puede tomar notas.
- Evitar el uso del argot técnico.
- Aplicar técnicas de resolución de conflictos.
- Permitir grandes pausas.
- Estimular el consenso del grupo.
- Estimular la participación de todos los usuarios impidiendo que unos dominen sobre otros.

RECOMENDACIONES EN UNA ENTREVISTA

Recomendaciones de ENTREVISTA
INTENTE:
- Ser amable.
- Escuchar atentamente.
- Dominar la situación.
- Sondear al entrevistado.
- Observar el lenguaje corporal.
- Sea paciente.
- Hacer que el entrevistado se sienta cómodo.
- Mantener el control propio.
EVITE:
- Proseguir la entrevista sin necesidad.
- Suponer que una respuesta está terminada o no conduce a ningún lado.
- Dar pistas verbales o no verbales.
- Usar argot.
- Poner de relieve sus opiniones personales.
- Hablar en vez de escuchar.
- Tener prejuicios sobre el asunto o el entrevistado.
- Grabar la conversación en cinta.

ENTREVISTAS

ENTREVISTAS

- Usar un lenguaje claro y conciso.
- No incluir la opinión propia como parte de la pregunta.
- Evitar preguntas largas o complejas.
- Evitar preguntas que supongan amenazas.
- No usar “ustedes” cuando se haga referencia a grupos de personas.

CUESTIONARIOS

CUESTIONARIOS

- Determine qué hechos y opiniones deben recabarse y de qué personas. Si el número de personas es muy amplio, considere un muestreo aleatorio.
- Determine qué tipo de cuestionario produciría mejores respuestas: Formato FIJO o LIBRE.
- Escriba las preguntas. Examínelas bien para evitar que contengan errores de expresión o que puedan dar lugar a interpretaciones erróneas.
- Asegúrese de que las preguntas no dan indicios de sus opiniones personales.
- Pruebe las preguntas en un grupo de muestra. Edite según aplique.

OBSERVACION

OBSERVACION

- QUÉ, CÓMO, CUANDO, DONDE y POR QUÉ.
- Obtener Autorización.
- Informar a los observados del propósito de la observación.
- Tratar de Pasar Inadvertido.
- Tomar notas durante y después.
- Revisar las notas con las personas adecuadas.
- NO INTERRUMPIR a las personas observadas en su trabajo.
- NO centrarse demasiado en las actividades triviales.
- NO tener prejuicios.

REVISION DE DOCUMENTACION

REVISION DOCUMENTACION

- Analizar gráficas
- Analizar Organigramas y Diagramas
- Diccionario de Proyectos
- Diseños (entradas, salidas, archivos)
- Documentación de Programas
- Manual de operaciones informáticas.
- Manual de Formación.
- Notas internas
- Estudios
- Actas
- Presupuestos
- Reclamaciones de Clientes
- Vitácoras de troubleshooting
- Registros de Cuentas
- Revisiones de Rendimiento
- Revisiones de Medidas de trabajo
- Informes Operativos
- Solicitudes de Proyectos
- Redacción del Plan Estratégico
- Política de la Empresa
- Procedimientos Operativos
- Instrucciones de tareas
- Formatos de transacciones reales
- Archivos manuales y digitales

RECOLECCION DE INFORMACION

RECOLECCION DE INFORMACION

- PASADO, PRESENTE, y FUTURO
- QUE, COMO, CUANDO, DONDE, PORQUÉ
- Revisar Documentación
- Observar operaciones
- Inyectar cuestionarios
- Entrevistas
- Diseño Conjunto de Aplicaciones (DCA)

RECOMENDACIONES

RECOMENDACIONES

Formato Sugerido de reporte

1- Introducción
2- Resumen de Requerimientos del sistema
3- Hallazgos
4- Recomendaciones
5- Estimados en Tiempo y Costo
6- Beneficios Esperados
7- Apéndices 

PLAN DE DESARROLLO TECNOLOGICO

PLAN DE DESARROLLO TECNOLOGICO

- Identifica Sistemas a Computadorizar
- Requisitos Mínimos de los equipos
- Informes a mejorar o implantar
- Fases del Proyecto
- Tareas del Proyecto
- Fechas de Entrega y Culminación

ESTUDIO DE VIABILIDAD

ESTUDIO DE VIABILIDAD

1- Económico (Costos)
2- Operacional
3- Técnico (Beneficios)
4- Tiempo

ESTUDIO DE NECESIDADES

ESTUDIO DE NECESIDADES

- Los recursos tecnológicos y humanos.
- La fecha de funcionalidad.
- El costo.
- Disponibilidad de Fondos.
- Compatibilidad Tecnológica y Estratégica.
- Cambios Futuros.

INVESTIGACION PRELIMINAR

INVESTIGACION PRELIMINAR

- Misión
- Visión
- Metas
- Objetivos
- Responsabilidades
- Servicios
- Recolectar Información

COMITE

COMITÉ de DESARROLLO DE SISTEMAS
- Gerenciales
- Analistas
- Programadores
- Entusiastas de Sistemas de Información
- Usuarios – Empleados
- Usuarios - Clientes

PLANIFICACION

FASE 1 PLANIFICACION
1- COMITÉ
2- Estudio Necesidades
3- Investigación Preliminar
4- Estudio de Viabilidad
5- Plan de Desarrollo Tecnológico
6- Recomendaciones
7- FORMATOS

FEASIBILITY STUDY example

ECONOMIC FEASIBILITY ANALYSIS
0 1 2 3 4 5 TOTALS
Build New System $0.00 $85,000.00 $85,000.00 $85,000.00 $85,000.00 $85,000.00
Discount rate (12 %) 1.000 0.8929 0.7972 0.7118 0.6355 0.5674
PV of Benefits $0.00 $75,893.00 $67,761.00 $60,501.00 $54,019.00 $48,231.00

NPV of Building New System $0.00 $44,643.00 $84,503.00 $120,092.00 $151,867.00 $180,239.00 $180,239.00

One-Time COSTS ($75,000)

Continue Maintaining Existing System
Recurring Costs ($35,000) ($35,000) ($35,000) ($35,000) ($35,000)
Discount rate (12 %) 1.000 0.8529 0.7972 0.7118 0.6355 0.5674
PV of Recurring Costs $0.00 ($31,250) ($27,902) ($24,912) ($22,243) ($19,860)

NPV of all COSTS ($42,500) ($67,946) ($90,666) ($110,952) ($129,064) ($145,236) ($201,167)


Overall NPV $105,239.00

ROI = Overall NPV / NPV of Costs 52.31%

Year of Project 0 1 2 3 4
Break-even Analysis
Yearly NPV Cash Flow ($75,000) $44,643 $39,860.00 $35,589.00 $31,776.00 $28,371.00
Overall NPV Cash Flow ($75,000) ($30,367) $9,503.00 $45,092.00 $76,867.00 $106,239.00


Break Even Ratio = (yearly NPV cash flow - general NPV cash flow) / yearly NPV cash flow
Break Even occurs in 1.8 years

0 1 2 3 4 5
Beneficios $0.00 $44,643.00 $84,503.00 $120,092.00 $151,867.00 $180,239.00
Costos $42,500 $67,946 $90,666 $110,952 $129,064 $145,236

ACTION LIST example

Pine Valley Furniture
WALKTHROUGH ACTION LIST

Session Coordinator: _______________________________
Project / Segment: _______________________________
Date and Time of Walkthrough: ___________________ Time: _________________

Fixed Issues raised in review

BASELINE PROJECT PLAN REPORT example

BASELINE PROYECT PLAN REPORT
1.0 INTRODUCTION
A. Project Overview – Provides an executive summary that specifies the project’s scope, feasibility, justification, resource requirements, and schedules. Additionally, a brief statement of the problem, the environment in which the system is to be implemented, and constraints that affect the project are provided.
B. Recommendation – Provides a summary of important findings from the planning process and recommendations for subsequent activities.
2.0 SYSTEM DESCRIPTION
A. Alternatives – Provides a brief presentation of alternative system configurations.
B. System Description – Provides a description of the selected configuration and a narrative of input information, tasks performed, and resultant information.
3.0 FEASIBILITY ASSESSMENT
A. Economic Analysis – Provides and economic justification for the system using cost-benefit analysis.
B. Technical Analysis – Provides a discussion of relevant technical risk factors and an overall risk rating of the project.
C. Operational Analysis – Provides an analysis of how the proposed system solves business problems or takes advantage of business opportunities in addition to an assessment of how current day-to-day activities will be changed by the system.
D. Legal and Contractual Analysis – Provides a description of any legal or contractual risks related to the project (e.g., copyright or nondisclosure issues, data capture or transferring, and so on).
E. Political Analysis – Provides a description of how key stakeholders within the organization view the proposed system.
F. Schedules, Timeline, and Resource Analysis – Provides a description of potential time frame and completion date scenarios using various resource allocation schemes.
4.0 MANAGEMENT ISSUES
A. Team Configuration and Management – Provides a description of the team member roles and reporting relationships.
B. Communication Plan – Provides a description of the communication procedures to be followed by management, team members and the customer.
C. Project Standards and Procedures – Provides a description of how deliverables will be evaluated and accepted by the customer.
D. Other Project-Specific Topics – Provides a description of any other relevant issues related to the project uncovered during planning.

INTERVIEW OUTLINE example

INTERVIEW OUTLINE

Interviewee:
Name of person being interviewed Interviewer:
Name of person leading interview
Location / Medium:
Office, conference room,
Or phone number. Appointment Date:
Start Time:
End Time:
Objectives:
What data to collect
On what to gain agreement
What areas to explore. Reminders:
Background / experience of interviewee
Known opinions of interviewee.
Agenda:
Introduction
Background on Project
Overview of Interview
Topics To Be Covered
Permission to Tape Record
Topic 1 Questions
Topic 2 Questions
…
Summary of Major Points
Questions from Interviewee
Closing Approximate Time:
1 minute
2 minutes

1 minute

5 minutes
7 minutes
…
2 minutes
5 minutes
1 minute
General Observations:
Interviewee seemed busy – probably need to call in a few days for follow-up questions since he gave only short answers. PC was turned off – probably not a regular PC user.
Unresolved Issues, Topics not Covered:
He needs to look up sales figures from 1999. He raised the issue of how to handle returned goods, but we did not have time to discuss.
Interviewee: Date:
Questions: Notes:
When to ask question, if conditional
Question number: 1
Have you used the current sales tracking system?
If so, how often?

If YES, go to Question 2 Answer:
Yes, I ask for a report on my product line weekly.

Observations:
Seemed anxious – may be overestimating usage frequency.
Question 2
What do you like least about the system? Answer:
Sales are shown in units, not dollars.
Observations:
System can show sales in dollars, but user does not know this.

PROJECT SCOPE example

PINE VALLEY FURNITURE Prepared by: Jim Woo
STATEMENT OF PROJECT SCOPE Date: September 18, 2001

General Project Information
Project Name: Customer Tracking System
Sponsor: Jackie Judson, VP Marketing
Project Manager: Jim Woo

Problem / Opportunity Statement:
Sales growth has outpaced the marketing department’s ability to accurately track and forecast customer buying trends. An improved method for performing this process must be found in order to reach company objectives.

Project Objectives:
To enable the marketing department to accurately track and forecast customer buying patterns in order to better serve customers with the best mix of products. This will also enable PVF to identify the proper application of production and material resources.

Project Description:
A new information system will be constructed that will collect all customer purchasing activity, support display and reporting of sales information, aggregate data, and show trends in order to assist marketing personnel in understanding dynamic market conditions. The project will follow PVF’s systems development life cycle.

Business Benefits:
Improved understanding of customer buying patterns.
Improved utilization of marketing and sales personnel.
Improved utilization of production and materials.

Project Deliverables:
Customer tracking system analysis and design.
Customer tracking system programs.
Customer tracking documentation.
Training procedures.

Estimated Project Duration:
5 months

REVIEW FORM example

Pine Valley Furniture
WALKTHROUGH REVIEW FORM

Session Coordinator: _______________________________________
Project / Segment: _______________________________________
Coordinator’s Checklist:
1. Confirmation with producer(s) that material is ready and stable: _______________
2. Issue invitations, assign responsibilities, distribute materials: [ ] Y [ ] N
3. Set date, time, and location for meeting:
Date: _____ / _____ / _____ Time: __________________ A.M. (circle one)
Location: _______________________________________________________________

Responsibilities Participants Can Attend ? Received Materials ?
Coordinator _________________________ [ ] Y [ ] N [ ] Y [ ] N
Presenter _________________________ [ ] Y [ ] N [ ] Y [ ] N
User _________________________ [ ] Y [ ] N [ ] Y [ ] N
Secretary _________________________ [ ] Y [ ] N [ ] Y [ ] N
Standards _________________________ [ ] Y [ ] N [ ] Y [ ] N
Maintenance _________________________ [ ] Y [ ] N [ ] Y [ ] N

Agenda:
____ 1. All participants agree to follow PVF’s Rules of a Walkthrough.
____ 2. New material: walkthrough of all material.
____ 3. Old material: item-by-item checkoff of previous action list.
____ 4. Creation of new action list (contribution by each participant)
____ 5. Group decision (see below)
____ 6. Deliver copy of this form to the project control manager.

Group Decision:
____ Accept product as-is.
____ Revise (no further walkthrough)
____ Review and schedule another walkthrough.

Signatures:

SYSTEM REQUEST Example

Pine Valley Furniture
SYSTEM SERVICE REQUEST

REQUESTED BY: Juanita Lopez Date: November 1, 2001
DEPARTMENT: Purchasing, Manufacturing Support
LOCATION: Headquarters, 1-322
CONTACT: Tel: 4-3267 FAX: 4-3270 e-mail: jlopez@hotmail.com
TYPE OF REQUEST URGENCY
[ X ] New System [ ] Immediate – Operations are impaired or opportunity lost
[ ] Systems Enhancement [ ] Problems exist, but can be worked around
[ ] System Error Correction [ X ] Business losses can be tolerated until new system installed
PROBLEM STATEMENT
Sales growth at PVF has caused greater volume of work for the manufacturing support unit within Purchasing. Further, more concentration on customer service has reduced manufacturing lead times, which puts more pressure on purchasing activities. In addition, cost-cutting measures force Purchasing to be more aggressive in negotiating terms with vendors, improving delivery times, and lowering our investments in inventory. The current modest systems support for manufacturing purchasing is not responsive to these new business conditions. Data are not available, information cannot be summarized, supplier orders cannot be adequately tracked and commodity buying is not well supported. PVF is spending too much on raw materials and not being responsive to manufacturing needs.
SERVICE REQUEST
I request a thorough analysis of our current operations with the intent to design and build a completely new information system. This system should handle all purchasing transactions, support display and reporting of critical purchasing data, and assist purchasing agents in commodity buying.
IS LIAISON Chris Martin (Tel. 4-6204 FAX: 4-6200 e-mail: cmartin@hotmail.com
SPONSOR: Sal Divario, Director, Purchasing
--------------------------------------------- TO BE COMPLETED BY SYSTEMS PRIORITY BOARD -----------------------------------------------
[ ] Request approved Assigned to ______________________________________
[ ] Recommend revision Start date _______________________________________
[ ] Suggest user development
[ ] Reject for reason: _________________________________________________________________
_________________________________________________________________
_________________________________________________________________