This CV template provides personal and contact details for Anate Halvorsen. It then lists her education qualifications including a matric in 1985 and a computer processing diploma in 1989. The experience section details her roles and responsibilities at various companies from 1990 to present. It emphasizes outputs like satisfying user requirements, ensuring data correctness, training users, and developing solutions on time. The skills section rates her proficiency in various technical and soft skills as basic, intermediate or advanced. Additional comments highlight her strengths in problem solving, data issues, and communicating with users.
This document discusses computer applications and their importance. It defines an application as a set of instructions and programs that improve a computer's functionality. The document outlines different types of applications including desktop applications like word processors and web browsers, as well as mobile apps. It explains that applications allow computers to perform specific tasks and that without applications, computers would not be functional.
The document provides a risk assessment of Blackboard and LJMU's online information systems. It models the systems and processes for handling assessment coursework. The assessment identified assets like Blackboard, the student information system, and online payment facilities. It analyzed risks to the confidentiality, integrity, and availability of these assets. The assessment was conducted according to the UK HMG Information Assurance Standard No. 1 to evaluate and suggest solutions to technical risks.
This document is a project report submitted by Alok Sharma for a summer training internship on a Console Based Billing System. The report provides details of the project including objectives to create a convenient billing solution and generate financial reports. It discusses the existing manual system and problems with it. The proposed computerized system aims to be more user friendly, support data sharing and modification, and strategic decision making through easy report generation. A feasibility analysis is also included covering technical, behavioral, economic and product aspects.
Neil Brittleton has over 20 years of experience in IT, primarily as a contractor developing and maintaining mainframe systems using languages like COBOL, PL/1, and Assembler. He has worked for several large financial institutions, most recently as a Senior Analyst at IPSL supporting mainframe systems that process checks for banks. Prior to that he held contracting roles developing and testing programs, managing teams, and assisting with system integrations and migrations. He has expertise in full life cycle development and a track record of delivering projects on time.
Event Management System Vb Net Project Report.pdfKamal Acharya
In present era, the scopes of information technology growing with a very fast .We do not see any are untouched from this industry. The scope of information technology has become wider includes: Business and industry. Household Business, Communication, Education, Entertainment, Science, Medicine, Engineering, Distance Learning, Weather Forecasting. Carrier Searching and so on.
My project named “Event Management System” is software that store and maintained all events coordinated in college. It also helpful to print related reports. My project will help to record the events coordinated by faculties with their Name, Event subject, date & details in an efficient & effective ways.
In my system we have to make a system by which a user can record all events coordinated by a particular faculty. In our proposed system some more featured are added which differs it from the existing system such as security.
The document defines an information system as a collection of technical and human resources that provide storage, computing, distribution, and communication for information required by an enterprise. It notes that a management information system provides information for managing an enterprise. The key components of an information system are hardware, software, data, procedures, and people. It then describes the functions and advantages of information systems for businesses, including allowing users to access and understand information quickly to respond effectively. Finally, it outlines the steps to build and maintain an information system, including planning, design, development/testing, implementation, operations/maintenance, and maintenance/disposition.
The document defines an information system as a collection of technical and human resources that provide storage, computing, distribution, and communication for information required by an enterprise. It notes that a management information system provides information for managing an enterprise. The key components of an information system are hardware, software, data, procedures, and people. It then describes the functions and advantages of information systems for businesses, including allowing users to access and understand information quickly to respond effectively. Finally, it outlines the steps to build and maintain an information system, including planning, design, development/testing, implementation, operations/maintenance, and maintenance/disposition.
This document discusses computer applications and their importance. It defines an application as a set of instructions and programs that improve a computer's functionality. The document outlines different types of applications including desktop applications like word processors and web browsers, as well as mobile apps. It explains that applications allow computers to perform specific tasks and that without applications, computers would not be functional.
The document provides a risk assessment of Blackboard and LJMU's online information systems. It models the systems and processes for handling assessment coursework. The assessment identified assets like Blackboard, the student information system, and online payment facilities. It analyzed risks to the confidentiality, integrity, and availability of these assets. The assessment was conducted according to the UK HMG Information Assurance Standard No. 1 to evaluate and suggest solutions to technical risks.
This document is a project report submitted by Alok Sharma for a summer training internship on a Console Based Billing System. The report provides details of the project including objectives to create a convenient billing solution and generate financial reports. It discusses the existing manual system and problems with it. The proposed computerized system aims to be more user friendly, support data sharing and modification, and strategic decision making through easy report generation. A feasibility analysis is also included covering technical, behavioral, economic and product aspects.
Neil Brittleton has over 20 years of experience in IT, primarily as a contractor developing and maintaining mainframe systems using languages like COBOL, PL/1, and Assembler. He has worked for several large financial institutions, most recently as a Senior Analyst at IPSL supporting mainframe systems that process checks for banks. Prior to that he held contracting roles developing and testing programs, managing teams, and assisting with system integrations and migrations. He has expertise in full life cycle development and a track record of delivering projects on time.
Event Management System Vb Net Project Report.pdfKamal Acharya
In present era, the scopes of information technology growing with a very fast .We do not see any are untouched from this industry. The scope of information technology has become wider includes: Business and industry. Household Business, Communication, Education, Entertainment, Science, Medicine, Engineering, Distance Learning, Weather Forecasting. Carrier Searching and so on.
My project named “Event Management System” is software that store and maintained all events coordinated in college. It also helpful to print related reports. My project will help to record the events coordinated by faculties with their Name, Event subject, date & details in an efficient & effective ways.
In my system we have to make a system by which a user can record all events coordinated by a particular faculty. In our proposed system some more featured are added which differs it from the existing system such as security.
The document defines an information system as a collection of technical and human resources that provide storage, computing, distribution, and communication for information required by an enterprise. It notes that a management information system provides information for managing an enterprise. The key components of an information system are hardware, software, data, procedures, and people. It then describes the functions and advantages of information systems for businesses, including allowing users to access and understand information quickly to respond effectively. Finally, it outlines the steps to build and maintain an information system, including planning, design, development/testing, implementation, operations/maintenance, and maintenance/disposition.
The document defines an information system as a collection of technical and human resources that provide storage, computing, distribution, and communication for information required by an enterprise. It notes that a management information system provides information for managing an enterprise. The key components of an information system are hardware, software, data, procedures, and people. It then describes the functions and advantages of information systems for businesses, including allowing users to access and understand information quickly to respond effectively. Finally, it outlines the steps to build and maintain an information system, including planning, design, development/testing, implementation, operations/maintenance, and maintenance/disposition.
The document provides guidance on implementing an enterprise system in 6 main steps: 1) Project management to set up the team and scope, 2) Preparation including training, data collection, and setup, 3) Build the customer-specific implementation by configuring the system, 4) Prepare for roll-out with user documentation and training, 5) Deployment and go-live, and 6) Support and manage enhancement requests after launch. It emphasizes preparation, training, and a phased approach to ensure success.
This document provides details about a student project to develop an online homemade food selling system (OHFSS). The objectives are to implement a food ordering system, design a system to help people save time and access healthy food, and test the system functionality. The project scope outlines the system's functions for customers, staff, and delivery persons. Methodology includes requirements analysis, design, implementation, testing, and user acceptance testing following the V-model. Hardware needs a laptop and printer while software includes Xampp server, PHP, and design tools.
Online job placement system project report.pdfKamal Acharya
Our project Expert.Com Job Placement System has been designed to help the millions of unemployed youth to get in touch with the major companies which would help them in getting the right kind of jobs and would also help the companies to get the appropriate candidates for appropriate jobs.
This document provides background information and context for developing an intranet mailing system. It discusses problems with the existing 2-tier system including high maintenance costs, placing logic on client systems, and security risks from storing data on clients. The document then outlines aims and objectives for a new intranet mailing system to provide secure internal communications. It also provides an overview of the spiral model software development methodology and considers it appropriate for this project.
The document discusses the disaster recovery planning process. It begins by explaining why companies often lack disaster recovery plans and view them as unnecessary. It then outlines the key steps in creating a disaster recovery plan, including assembling a team, defining business goals, identifying critical systems, conducting risk analysis, documenting the plan, and testing the plan on a regular basis. Frequent testing is important to ensure the plan will work in an actual disaster situation.
Tan Chuan Leong has over 3 years of experience as a Software Engineer and Technical Analyst at Accenture Solution Sdn Bhd. He holds a Bachelor's Degree in Information Systems Engineering and Advanced Diploma in Information Systems Engineering from Tunku Abdul Rahman College. His skills include Java, C#, SQL, and networking. Currently he supports and enhances the Distribution Management System for Nestle and handles the Unza project independently, providing technical support, developing changes, and analyzing business impacts of requests.
This presentation was presented at HR 2007 in Los Vegas. It shows the top 10 reasons behind Intervoice\'s success with its global SAP HCM implementation.
Running Header 1APPLICATION DEVELOPMENT METHODS2.docxrtodd599
Running Header: 1
APPLICATION DEVELOPMENT METHODS 2
Unit 1 Group Project
Application Development Methods
Group 4
John Holmberg, Sean Austin, Christian Dillon, Charles Williams, Matthew Serdy, Frank Opoku
April 10, 2019
IT487 – IT Capstone 1
Nolyn Johnson
Table of Contents
Section 1 - Overview of Company and Client Business Case 3
Section 2 - Application Requirement Elicitation Strategy 5
Section 3 - System Components and Design Requirements 7
Section 4 - Methodology for Application Development Process 8
Section 5 - Complete Features and Trade-off Analysis 10
Section 6 - Milestones and Deliverables Based on Date and Dependencies 11
Section 7 - System Architecture Aligned with System Requirements 12
Section 8 - Technical Design Document 13
Section 9 - Design Review Checklist 14
Section 10 - Testing and Deployment 15
References 16
Section 1 - Overview of Company and Client Business Case
The company Education Information Systems. (EiS) is an information and management company that specializes in the creation and care of large-scale educational information and technology systems. EiS has implemented and managed systems ranging from the pre-K to 12th year primary school systems, and is developing larger scale systems to facilitate collegiate, graduate and post graduate educational institutions. EiS is a privately held organization that has the primary focus of providing the best possible systems to help grow the educational sector. Previous clients have implemented system wide software replacement and upgrades. With a stellar track record of previous educational institutions, and references, EiS has completed all the projects on time, and within budgetary guidelines. All problem issues or negative feedback from clients were handled in professional and timely manner that resulted in a completely satisfied client.
Moving toward post high school educational institutions, EiS is working with an extremely talented development team to move into the graduate and post graduate sector with ease. With new projects being developed, and more clients, EiS also works to recruit the best talent in the development, and technical aspects of information technology.
The information system to be developed by EiS for the institution will allow for all student, and faculty to store, share, and secure data. Utilizing a web-based UI, the information will be easily accessed, with the proper credentials. Data can be shared among staff, and students with preferences designed to mitigate corruption of data, loss of information, especially personal and financial information. All faculty and staff can be added to the application via an admin portal and all security is designated there. All remote access to the application will require a 2 factor
authentication system for another level of security to ensure that the proper access protocols are being followed. All information that is stored will be designed to the student or faculty member, and kept throughout the .
Kavitha Elangovan is a PeopleSoft Technical Consultant with over 4 years of experience implementing PeopleSoft HCM systems. She has extensive experience with PeopleTools, Application Designer, PeopleCode, Application Engine, and other PeopleSoft development tools. Some of her project experience includes implementing Global Absence Management and other modules for Pfizer in Mexico. She also has experience with an European Integration Project and Long Term Incentive projects for Pfizer. Additionally, she worked on a PeopleSoft HCM 9.0 implementation for National Insurance Company including developing custom bolt-on modules.
An innovation team at Southcoast Health developed several technical solutions to address unique issues that arose during their enterprise EMR implementation over 21 months. These included a provider management system, patient movement matrix, position control verification tool, and integrated ambulance rotation requests. The innovation team's work helped streamline workflows and provide end users access to necessary information directly within the EMR. Their projects have generated over $12 million in ROI from an investment of $1.5 million.
The document describes a heuristic evaluation of the WhenIwork scheduling app. It discusses the research methodology, which involved observing Jakob Nielsen's generic heuristics as a baseline, considering domain-specific details and typical users, and creating new app-specific heuristics. A table shows Nielsen's heuristics and proposed heuristics for WhenIwork. The evaluation found three violations of heuristics: error prevention due to confusing tables, flexibility due to some navigation confusion, and offering help due to long wait times for technical support.
1Running Head Business ProjectSection 1 Business Requirement.docxfelicidaddinwoodie
1
Running Head: Business Project
Section 1: Business Requirements Document
I. Describe the scope and analyze how to control the scope.
Scope:
We live in computer age where businesses no more bound by borders or limited clientage. Computer and fast technology has renovated the Project's scope can be defined as such element in project that explains the boundaries of the project, set responsibilities for each team member and describe the procedures for how completed work will be verified and how it will be approved.
Meetup help the people together in thousands of cities to do what they want to do in life. Major scope is to give the human being a happiness and peace of mind so that no one gets disappointed that he never got a chance to do what he want to do in his life. It is based on a very simple single idea that is when we get together and do such tasks that matter to us or appeal us most, we’re doing our best. It's all about the central idea or major chunk of scope of Meetup. It assist the people together to do, search, teach and learn the things that help them to live long and what they desire most to do. Meetup now want to increase its scope by setting offices in main cities and want to do extensive advertisement so that more people know about services of company and connect with it.
How to Control Scope process
Changing a scope is an ongoing process that starts just after creation of baseline.
Control Scope Inputs
Five inputs are included in control scope process
1. Project management plan.
In this step scope baseline consisting of the WBS codes WBS dictionary as well as the project scope statement is analyzed. This phase describes how to control scope when the change control plan will intimate about project change control system.
2. Work performance information.
In this phase information is provided on deliverable status and it describes which deliverables are ready to launch and which one are currently work in progress, and how much work is still pending. This phase contains information related to any issues and risks that the development team is expected to face for particular deliverables or products.
3. Requirements documentation.
This is very important phase in input process as when a change request is made the requirements documentation acts as a reference to memorize what was originally agreed so that the change could be detected against the regional requirement.
4. Requirements traceability matrix.
It helps the project manager to estimate about the value of change that is required and the regional baseline that is already finalized and why this change is so important for this project. It assist him to identify source of change and he will consult about this change from the stakeholders who are expected to affect by this change.
5. Organizational process assets.
This will normally cover any particular policies and procedures that have been laid down by the delivery organization regarding scope manage ...
The document provides an overview of a hospital management system project. It describes the existing manual system and its limitations. The proposed computerized system aims to overcome these limitations by providing features such as unique patient IDs, search capabilities, and automated billing. The system will use Visual Basic 6.0 for the front end, MS Access as the back end database, and be installed on PCs meeting the specified hardware requirements. It will allow secure, fast, and efficient management of hospital operations and data.
This document discusses information systems and their design. It defines information as organized data including text, numbers, audio, video and images. The key components of an information system are processes, data, hardware, software and people. There are several types of information systems including management information systems, transaction processing systems, decision support systems, executive information systems and expert/artificial intelligence systems. The design of information systems involves logical design, physical design, construction and testing. Logical design translates user requirements into functions and structures to organize information. Data flow diagrams and data dictionaries are important tools used in the design process.
The project involved migrating data from 4 instances of the legacy ERP Syspro system to a single SAP system for ABB South Africa. Over 150,000 records needed to be consolidated and cleansed. The solution developed an in-house .NET system and SQL database to consolidate the data. The data was extracted to Excel for cleansing by business users. The migration was completed successfully within budget and delivered clean data for import to the new SAP system. Lessons included dedicating super users solely to data cleansing.
This document describes a Mess Management Android application created by group members Anand Bhagyawant, Samarth Kadam, and Pavanraj Jadhav. The app aims to automate mess operations in educational institutions and hostels by digitizing tasks like student data management and bill payment tracking. It contains modules for mess managers and students. The manager module allows adding, updating, and viewing student profiles and bills, and sending payment reminders. The student module permits viewing daily menus and submitting complaints or suggestions. The document outlines the app's methodology, data flow diagrams, technical details, and concludes the app will efficiently manage mess operations with less time and effort compared to manual methods.
Synopsis on inventory_management_systemDivya Baghel
This document provides a synopsis for an inventory management system created in VB.NET. It discusses the existing manual inventory system and proposes developing a computerized system. The proposed system would track inventory levels and transactions. It describes the system requirements, feasibility analysis, and modules to be included. The main objectives are to maintain appropriate inventory levels to avoid excess or shortage, and to make the system user-friendly, secure, and fast.
The document provides an overview of the system architecture project for an education information systems company. It includes 10 sections that cover: an overview of the company and client case, requirements elicitation strategy, system components and design requirements, application development methodology, features and tradeoff analysis, milestones and deliverables, system architecture aligned with requirements, technical design document, design review checklist, and testing and deployment. The project aims to develop an information system for a higher education institution to allow secure sharing and storage of student and faculty data through a web-based interface.
The document provides guidance on implementing an enterprise system in 6 main steps: 1) Project management to set up the team and scope, 2) Preparation including training, data collection, and setup, 3) Build the customer-specific implementation by configuring the system, 4) Prepare for roll-out with user documentation and training, 5) Deployment and go-live, and 6) Support and manage enhancement requests after launch. It emphasizes preparation, training, and a phased approach to ensure success.
This document provides details about a student project to develop an online homemade food selling system (OHFSS). The objectives are to implement a food ordering system, design a system to help people save time and access healthy food, and test the system functionality. The project scope outlines the system's functions for customers, staff, and delivery persons. Methodology includes requirements analysis, design, implementation, testing, and user acceptance testing following the V-model. Hardware needs a laptop and printer while software includes Xampp server, PHP, and design tools.
Online job placement system project report.pdfKamal Acharya
Our project Expert.Com Job Placement System has been designed to help the millions of unemployed youth to get in touch with the major companies which would help them in getting the right kind of jobs and would also help the companies to get the appropriate candidates for appropriate jobs.
This document provides background information and context for developing an intranet mailing system. It discusses problems with the existing 2-tier system including high maintenance costs, placing logic on client systems, and security risks from storing data on clients. The document then outlines aims and objectives for a new intranet mailing system to provide secure internal communications. It also provides an overview of the spiral model software development methodology and considers it appropriate for this project.
The document discusses the disaster recovery planning process. It begins by explaining why companies often lack disaster recovery plans and view them as unnecessary. It then outlines the key steps in creating a disaster recovery plan, including assembling a team, defining business goals, identifying critical systems, conducting risk analysis, documenting the plan, and testing the plan on a regular basis. Frequent testing is important to ensure the plan will work in an actual disaster situation.
Tan Chuan Leong has over 3 years of experience as a Software Engineer and Technical Analyst at Accenture Solution Sdn Bhd. He holds a Bachelor's Degree in Information Systems Engineering and Advanced Diploma in Information Systems Engineering from Tunku Abdul Rahman College. His skills include Java, C#, SQL, and networking. Currently he supports and enhances the Distribution Management System for Nestle and handles the Unza project independently, providing technical support, developing changes, and analyzing business impacts of requests.
This presentation was presented at HR 2007 in Los Vegas. It shows the top 10 reasons behind Intervoice\'s success with its global SAP HCM implementation.
Running Header 1APPLICATION DEVELOPMENT METHODS2.docxrtodd599
Running Header: 1
APPLICATION DEVELOPMENT METHODS 2
Unit 1 Group Project
Application Development Methods
Group 4
John Holmberg, Sean Austin, Christian Dillon, Charles Williams, Matthew Serdy, Frank Opoku
April 10, 2019
IT487 – IT Capstone 1
Nolyn Johnson
Table of Contents
Section 1 - Overview of Company and Client Business Case 3
Section 2 - Application Requirement Elicitation Strategy 5
Section 3 - System Components and Design Requirements 7
Section 4 - Methodology for Application Development Process 8
Section 5 - Complete Features and Trade-off Analysis 10
Section 6 - Milestones and Deliverables Based on Date and Dependencies 11
Section 7 - System Architecture Aligned with System Requirements 12
Section 8 - Technical Design Document 13
Section 9 - Design Review Checklist 14
Section 10 - Testing and Deployment 15
References 16
Section 1 - Overview of Company and Client Business Case
The company Education Information Systems. (EiS) is an information and management company that specializes in the creation and care of large-scale educational information and technology systems. EiS has implemented and managed systems ranging from the pre-K to 12th year primary school systems, and is developing larger scale systems to facilitate collegiate, graduate and post graduate educational institutions. EiS is a privately held organization that has the primary focus of providing the best possible systems to help grow the educational sector. Previous clients have implemented system wide software replacement and upgrades. With a stellar track record of previous educational institutions, and references, EiS has completed all the projects on time, and within budgetary guidelines. All problem issues or negative feedback from clients were handled in professional and timely manner that resulted in a completely satisfied client.
Moving toward post high school educational institutions, EiS is working with an extremely talented development team to move into the graduate and post graduate sector with ease. With new projects being developed, and more clients, EiS also works to recruit the best talent in the development, and technical aspects of information technology.
The information system to be developed by EiS for the institution will allow for all student, and faculty to store, share, and secure data. Utilizing a web-based UI, the information will be easily accessed, with the proper credentials. Data can be shared among staff, and students with preferences designed to mitigate corruption of data, loss of information, especially personal and financial information. All faculty and staff can be added to the application via an admin portal and all security is designated there. All remote access to the application will require a 2 factor
authentication system for another level of security to ensure that the proper access protocols are being followed. All information that is stored will be designed to the student or faculty member, and kept throughout the .
Kavitha Elangovan is a PeopleSoft Technical Consultant with over 4 years of experience implementing PeopleSoft HCM systems. She has extensive experience with PeopleTools, Application Designer, PeopleCode, Application Engine, and other PeopleSoft development tools. Some of her project experience includes implementing Global Absence Management and other modules for Pfizer in Mexico. She also has experience with an European Integration Project and Long Term Incentive projects for Pfizer. Additionally, she worked on a PeopleSoft HCM 9.0 implementation for National Insurance Company including developing custom bolt-on modules.
An innovation team at Southcoast Health developed several technical solutions to address unique issues that arose during their enterprise EMR implementation over 21 months. These included a provider management system, patient movement matrix, position control verification tool, and integrated ambulance rotation requests. The innovation team's work helped streamline workflows and provide end users access to necessary information directly within the EMR. Their projects have generated over $12 million in ROI from an investment of $1.5 million.
The document describes a heuristic evaluation of the WhenIwork scheduling app. It discusses the research methodology, which involved observing Jakob Nielsen's generic heuristics as a baseline, considering domain-specific details and typical users, and creating new app-specific heuristics. A table shows Nielsen's heuristics and proposed heuristics for WhenIwork. The evaluation found three violations of heuristics: error prevention due to confusing tables, flexibility due to some navigation confusion, and offering help due to long wait times for technical support.
1Running Head Business ProjectSection 1 Business Requirement.docxfelicidaddinwoodie
1
Running Head: Business Project
Section 1: Business Requirements Document
I. Describe the scope and analyze how to control the scope.
Scope:
We live in computer age where businesses no more bound by borders or limited clientage. Computer and fast technology has renovated the Project's scope can be defined as such element in project that explains the boundaries of the project, set responsibilities for each team member and describe the procedures for how completed work will be verified and how it will be approved.
Meetup help the people together in thousands of cities to do what they want to do in life. Major scope is to give the human being a happiness and peace of mind so that no one gets disappointed that he never got a chance to do what he want to do in his life. It is based on a very simple single idea that is when we get together and do such tasks that matter to us or appeal us most, we’re doing our best. It's all about the central idea or major chunk of scope of Meetup. It assist the people together to do, search, teach and learn the things that help them to live long and what they desire most to do. Meetup now want to increase its scope by setting offices in main cities and want to do extensive advertisement so that more people know about services of company and connect with it.
How to Control Scope process
Changing a scope is an ongoing process that starts just after creation of baseline.
Control Scope Inputs
Five inputs are included in control scope process
1. Project management plan.
In this step scope baseline consisting of the WBS codes WBS dictionary as well as the project scope statement is analyzed. This phase describes how to control scope when the change control plan will intimate about project change control system.
2. Work performance information.
In this phase information is provided on deliverable status and it describes which deliverables are ready to launch and which one are currently work in progress, and how much work is still pending. This phase contains information related to any issues and risks that the development team is expected to face for particular deliverables or products.
3. Requirements documentation.
This is very important phase in input process as when a change request is made the requirements documentation acts as a reference to memorize what was originally agreed so that the change could be detected against the regional requirement.
4. Requirements traceability matrix.
It helps the project manager to estimate about the value of change that is required and the regional baseline that is already finalized and why this change is so important for this project. It assist him to identify source of change and he will consult about this change from the stakeholders who are expected to affect by this change.
5. Organizational process assets.
This will normally cover any particular policies and procedures that have been laid down by the delivery organization regarding scope manage ...
The document provides an overview of a hospital management system project. It describes the existing manual system and its limitations. The proposed computerized system aims to overcome these limitations by providing features such as unique patient IDs, search capabilities, and automated billing. The system will use Visual Basic 6.0 for the front end, MS Access as the back end database, and be installed on PCs meeting the specified hardware requirements. It will allow secure, fast, and efficient management of hospital operations and data.
This document discusses information systems and their design. It defines information as organized data including text, numbers, audio, video and images. The key components of an information system are processes, data, hardware, software and people. There are several types of information systems including management information systems, transaction processing systems, decision support systems, executive information systems and expert/artificial intelligence systems. The design of information systems involves logical design, physical design, construction and testing. Logical design translates user requirements into functions and structures to organize information. Data flow diagrams and data dictionaries are important tools used in the design process.
The project involved migrating data from 4 instances of the legacy ERP Syspro system to a single SAP system for ABB South Africa. Over 150,000 records needed to be consolidated and cleansed. The solution developed an in-house .NET system and SQL database to consolidate the data. The data was extracted to Excel for cleansing by business users. The migration was completed successfully within budget and delivered clean data for import to the new SAP system. Lessons included dedicating super users solely to data cleansing.
This document describes a Mess Management Android application created by group members Anand Bhagyawant, Samarth Kadam, and Pavanraj Jadhav. The app aims to automate mess operations in educational institutions and hostels by digitizing tasks like student data management and bill payment tracking. It contains modules for mess managers and students. The manager module allows adding, updating, and viewing student profiles and bills, and sending payment reminders. The student module permits viewing daily menus and submitting complaints or suggestions. The document outlines the app's methodology, data flow diagrams, technical details, and concludes the app will efficiently manage mess operations with less time and effort compared to manual methods.
Synopsis on inventory_management_systemDivya Baghel
This document provides a synopsis for an inventory management system created in VB.NET. It discusses the existing manual inventory system and proposes developing a computerized system. The proposed system would track inventory levels and transactions. It describes the system requirements, feasibility analysis, and modules to be included. The main objectives are to maintain appropriate inventory levels to avoid excess or shortage, and to make the system user-friendly, secure, and fast.
The document provides an overview of the system architecture project for an education information systems company. It includes 10 sections that cover: an overview of the company and client case, requirements elicitation strategy, system components and design requirements, application development methodology, features and tradeoff analysis, milestones and deliverables, system architecture aligned with requirements, technical design document, design review checklist, and testing and deployment. The project aims to develop an information system for a higher education institution to allow secure sharing and storage of student and faculty data through a web-based interface.
1. CURRICULUM VITAE TEMPLATE
PERSONAL DETAILS
NAME
Anate
SURNAME
Halvorsen
IDENTITY NUMBER
670401 0006 089
ADDRESS : 93 Elise Road
FONTAINEBLEAU
RANDBURG
2194
CONTACT NUMBER : 082 899 2247
EMAIL ADDRESS : anate.halvorsen@gmail.com
DATE OF BIRTH : 1 April 1967
IDENTITY NUMBER : 670401 0006 089
AGE : 48
MARITAL STATUS : Married
HOME LANGUAGE : Afrikaans
OTHER LANGUAGES : English (speak, read, write and understand)
NATIONALITY : South African Citizen
DRIVER’S LICENSE : Code A1 & EB
CRIMINAL OFFENCES : None
2.
3. EDUCATION
QUALIFICATION INSTITUTION YEAR COMPLETED
Matric High school Frans du Toit 1985
National Diploma – Computer Date
Processing
Technikon Pretoria 1989
EXPERIENCE
When completing the outputs section below, think about the tangible and measurable outputs that
you are/were responsible for (max 6-8). Focus on overall accountabilities rather than tasks. The
statements should represent what you do and how you do it. List the outputs in terms of importance
starting from the most important output.
COMPANY Liberty Health
POSITION Senior Developer
TIMEFRAME 2011 to current
List the main outputs of the position below:
1. Satisfaction of user requirements, good relationship and communication with user.
Produce professional solutions at all time and ensure that user feels comfortable to
contact you with any questions or uncertainties – it will add to correct output and save
time. Make sure other developers are not busy with same programs in case of an
enhancement to prevent overriding of their code.
2. Request can be customization, development, modification, data manipulation or a
project over a period of time. During development, after I’ve done the investigation and
analysis, I keep close communication with user to ensure understanding that both
parties are in sync and also to prevent comebacks and make the user feel part of the
enhancement / new development, ensure fully understanding of request. Make
suggestions, that I might pick up during investigation process, in order to make the
output more valuable for the client.
3. Correctness of output – reports / data extracts – use different testing scenarios and
ensure my changes do not affect any other reports / extracts
4. Data manipulation where needed for data correctness as soon as possible and fixing of
origin where data incorrectness may occur – data integrity is of utmost importance
5. Data capturing on screens – all security and user checks in place. Prevention of
capturing incorrect data. Sufficient help messages for users. Make capturing and
enquiries as easy / understandable to user to ensure correctness of data capturing as
far as possible to make the user feel in control and comfortable with his work
6. Data Security on all screens, reports and data extracts on current and new modules /
enhancements, and again, make sure it does not affect other areas
4. 7. Keep to development and projected dates by doing proper planning that includes
investigation and analysis before starting of development. I might realise that I need
more detailed information from the user before starting development to ensure user
satisfaction and understanding, that will lead to contact user – do training trough out
this different stages to ensure user understand
8. Make use of available functions and given indexesfor fast output results
9. Intensive user training. Follow up with user after user training, even after development
has been taken to the live environment. User satisfaction!
10. Close involvement with migration project. It involved programs, and mostly the data
transfer integrity. I wasresponsible for correcting programs that gave incorrect data
outputs and the migration thereof, fix the incorrect data, suggested index changes on
the Linux side, so that the data that wastransferred to Linux was 100% correct and
balanced on both the HP and Linux environments with going live on Linux.
11. Currently busy with Report Motorisation – Compiling Specification documents of
current Medware Reports (full Medware system, all modules)
COMPANY Proteus Software
POSITION Analyst Programmer / System Analyst
TIMEFRAME 2008 to 2009
List the main outputs of the position below:
1. On the system analyst side: If they want new modules in system, do JAD sessions with
key users to determine requirement, put together “brown paper”
2. Do analysis of JAD session outcome and the feasibility there off – how will it impact the
rest of the system and interfaces seeing they used SAP as financial system
3. Draw up “white paper” and have another discussion session with key users and
managers to discuss possible problems and work together on solutions
4. Set up flow chart from final decision mentioned in point 3
5. Work together with programmer to discuss required output, updates, interfaces and
why to go forward
6. During development / programming, give necessary assistance to programmer
7. If needed, do some of development and constantly keep contact with user and affected
parties
8. Training and implementation. User satisfaction!
5. COMPANY MIP
POSITION Analyst Programmer
TIMEFRAME 2005 to 2008
List the main outputs of the position below:
1. Pretty much the same as Liberty, I was working in the Life Insurance team
2. When requests get assigned to me, the system analysis process was done. It can be
customization, development, modification or data manipulation
3. Make contact with the client, discuss the system analysis that was done before starting
with development. If needed, relook at the analysis with client or go back to system
analyst. Suggest
4. Do own flow chart, investigation and planning before development started. Ask if
something is not clear.
5. Stay in contact with client to ensure correctness of understanding. Design easy and
understandable screens where applicable and do all data checks for data correctness.
Data fixes when needed and prevent by fixing origin that create data incorrectness
6. Do testing with user during development, depending on how complex the request is.
Always ensure the output is correct and to the client’s satisfaction
7. Make suggestions if you pick up an area where it might be suitable
8. Testing, training and implementation. User satisfaction!
COMPANY EOH
POSITION JDEdwards Consultant
TIMEFRAME 2004 to 2005
List the main outputs of the position below:
1. Request can be customization, development, modification or data manipulation
2. Most requests of an ERP system consist of customization, modification and data
manipulation. In case of a module not supported by JDE, development will be done
3. My main tasks were customisation, development of reports and data manipulation
4. With the tasks mentioned above, I will follow the same rout as currently, to get the user
involved and informed
5. Ensure at all times the correctness of data and easy, understandable menus and
screens.
6. With an ERP system, you have to create new reports and screens in case of
customisation, seeing that an upgrade from the ERP suppliers will rese t your
customisation on screens and reports
6. 7. Interfaces was written and maintained by me between modules that is developed
external to the JDE package
8. User satisfaction!
COMPANY
Foskor
POSITION
a) Programmer
b) Analyst Programmer
c) Business Analyst
TIMEFRAME
a) 1990 to 1993
b) 1993 to 1995
c) 1995 to 2003
List the main outputs of the position below:
1. Foskor paid my studies, so I had to start my career there. They were using a Cobol in-
house written system, running on ICL. I was mostly involved in maintenance and small
system enhancements; Cobol was one of my main subjects, so I could start straight
away. At this stage my supervisor gave the system changes that was needed to me,
and gave me assistance
2. I also start writing interface programs where I did the feasibility on, after the JAD
sessions were done.
3. There were a few managersthat used Lotus 123 for their monthly reports. I started
rewriting those in DBASE and the interfaces between ICL and my DBASE systems
4. The big change happened in 1993 when there was decided the re-write the whole Cobol
system in Powerhous – Core as well asnon-core. The ICL was replaced with a VAX
machine with VMS as operating system and Interbase as database. I also received
training in that.
5. The team, 6, received about 6 months of intensive in-house training in Powerhouse,
while still maintaining the Cobol system
6. With the start of the re-writing, I wastrained to use Infomet Methodology to do the data
population that had to be transferred from the Cobol system to the Powerhouse system
7. The systems I was given included the Personnel Distribution that linked to external
entities like the municipality, ABSA bank, Mine clubs and the Payroll system, so that all
these deductions was done in the Payroll system. I did the JAD sessions, feasibility
studies, analysis, GAP analysis, contact with internal and external parties,
development, testing, training and implementations of these systems / interfaces. I also
did the interface / integration between the Payroll system and the General Ledger and
Personnel Debtors systems on the VAX system (Powerhouse).
8. Smaller systems that had to be developed as well includes the housing system, safety
system with ISO requirements, Loan system, Cashbook system, Authorisation system
Menu system administration for core integrated systems. With these systems I was
also responsible from JAD sessions up to analysis, development, testing, training and
implementation. All of these included Input and Enquiry screens, data processing,
reports and interfaces.
9. I did the Transportations module for the Procurement system that interfaced with the
Creditors and General Ledger subsystems. It involved the analysis, development,
testing and implementation. No user training wasneeded, it was an automated
process, so my user was the Financial Manager that was involved when I did the
analysis.
7. 10. I did maintenance and fault detection on the following systems: Core financial system,
total system integration between Core Financial systems and subsystems, Procurement
system – including inventory control and movement, issuing, receiving, COD receiving,
tenders and the mining projects.
11. I was mostly involved in analysis, development and data fixing with the assistance of
the BA’s of the different modules.
12. I did 2 internal data audits, using data extracts done in Powerhouse, and excel.
13. I did 1 external data audit with KPMG by providing them with system data via data
extracts from the Powerhouse system
14. In 1999 the team started with the migration to JDEdwards, where I wasthe Business
Analyst for Procurement and the financial side of the Payroll system with integration
with the General Ledger and Personnel Debtors subsystem. It involved JAD sessions
with Managers and key users and GAP analysis at first, and later on development for
user requirement, testing, training and implementation.
15. User satisfaction!
SKILLS
The skills below could be gained through formal / informal education or experience and involves the
application of techniques or methodologies. Define the level of skill that you have for the below
mentioned skills. Should there be additional skills you would like to add, please do so at the bottom of
the table.
Skill Basic Intermediate Advanced
Computer Literacy X
Verbal Communication Skills X
Written Communication Skills X
Report writing skills (Systems) X
Listening Skills X
Client Centric X
Analytical Skills X
Problem solving skills X
Coaching skills X
Risk Management Skills X
Interpersonal skills (influencing skills) X
8. Interpersonal skills (conflict resolution) X
Networking skills X
Supervisory/team leadership (Mentor) X
Powerhouse X
Cobol X
Programming in Progress X
Powerhouse Programming- beginners and
advance
X
Powerhouse Advanced for new features X
Delphi Programming X
Interbase Database X
Infomet Methodology – IIM, ASS1, ASS2,
Workshop, JAD
X
9. ADDITIONAL COMMENTS
Should you have any additional information you would like to add about yourself or your skills,
knowledge etc., please do so below:
My strength is in problem solving – every problem is an opportunity and there will be a solution.
Top of my list: working with data problems, ex. Data audits, data integrity, data fixing, fault detection
and fixing. I am committed to my work, and proud of it. I enjoy working with users of all levels and to
communicate with them, help them sorting out concerns until they understand and create solutions to
make their work easier, more understandable and easy to report on, in order to save them time. I
have a gift of staying calm and think clearly under stressful situations. Creative thinking and initiative
are also part of my problem solving. What counts in my favour when it comes to experience, is
thanks to the diversity of systems that I had the privilege to work on, developed, maintained etc. as
well as the people I worked with and users from all levels.
I thank you for this opportunity.
DECLARATION
Statement Yes No
I declare that all the information provided (including any attachments) is complete
and correct to the best of my knowledge. I understand that any false information
supplied could lead to my application being disqualified.
X