My take on the University Enrollment System..

{ Posted on 11:37 AM by Ariel Serenado }
1 comments
Each and every year, the enrollment process of the university is being changed to really cover the student's needs which is to have an easy flow of enrollment hence, will give convenience to every one involved in the process. The fact that the university is giving much effort to eradicate the past problems, it is right to give compliments in their part for, they are really looking forward on giving due services to the students. However, it could not be denied that the process the university is implementing appears to have some weaknesses on it thus, letting the students to criticize it and even marked it with “needs improvement”. End-users view on the process must be taken into consideration especially, that these end-users are the resources of the university and with that, it is a must to take “our” views on what is going on with the current process for it might serve as the stepping stone, if not the best but at least better implementation that the past few years.

In relation to my answer in the previous assignment, the enrollment process really improved since the time I entered the premises of the university up to this date, and as what I have mentioned from my last assignment there are still instances that the process really needs improvement. One thing which I considered a weakness in the process is that, there is no such unified submission of requirements or fees on the day of enrollment. In my case, I really wanted to have a unified processing of this certain process for somehow it could lessen the burden of the students to visit different divisions of the university with just one purpose which is to pay. For me, it is sometimes not ideal to do different tasks in different places with a single purpose when you can actually do it in a certain place, aside from it reduces time for students, and it also reduces operational cost; for the university will need to utilize another resources when the current resource can be utilized to cater two distinct tasks with a single purpose.


Furthermore, in the idea of improving the university enrollment process, it does not only require another set of enrollment process but also everyone involved in the process must take an action to make all things right.

Enrollment Process Observation...

{ Posted on 4:18 PM by Ariel Serenado }
1 comments

One of the processes that we can associate when we talk about a school or a certain educational institution is the Enrollment process. Enrollment process may differ in terms of the number of steps to be followed, or the requirements to be submitted but the main point of the enrollment is to admit a student who satisfactorily satisfied the standards, the policies, the guidelines and of course the requirements of the school. As to how this kind of process of a school will be implemented, it really depends to the people governing a school. In big universities especially state universities, it is important that the enrollment process must be systematic and orderly implemented to avoid chaotic scenario. In enrollment there is such thing as enrollment procedure that the school must attach in any strategic locations of the university for it serves as the guidelines of the students especially the incoming ones. This enrollment procedure may be in text format or flow charts that directly illustrate the flow of the process from the very beginning to the end of the process. It is important to clearly define all the items or the components in an enrollment system for a systematic flow of the process.

Let’s take the case of USeP for this assignment.

As a student of USeP I have that greater access to experience the enrollment process of the school, especially now that I have reached the 4 years of residency probably, I can criticized or state my observations as to how good or systematic the process is. When I took the challenge to enroll in the university I am not the kind of student who keenly observed the process of enrollment for what I am looking forward is to finish the process even how much time I spent for each step however, for the last few years and for this semester S.Y 2010-2011 I have these following observations on the enrollment process:

1. There is no such Unified collection of fees (miscellaneous, tuition fees). As though there are different university-accredited organizations in the school to collect fees, payment should be done in a single venue to make the process centralized. This also helps the process on submission or pertinent documents, sometimes these receipts are asked and sometimes it takes time for a student to present the receipt, whereas if the fees are reflected in a single document then the enrollment officer can just glance into the document whether the student paid the fees or not.
2. Limited number of windows to cater students, especially in finance division. This is one problem that students would like to be answered. This problem gives a long queue especially for peak period of enrollment, it is not ideal to cater student in university with only 2 windows with of course 2 officers to receive transactions.
3. Renewal of scholarship takes sometime. This is one process in the enrollment which causes long queue in other processes. Though this process depends on the benefactor but since it is part of the university enrollment process, then it must be settle by the governing body to make it systematic thus, will not cause any enrollment delays and extensions.

4. Submission of requirements is not centralized. The University and Guidance office (UGTO) once posted and reminded students not to give their original documents to any department except the registrar for, the office of registrar will not be liable of lost documents once those documents are not submitted in the registrar’s office. It seems that there colleges / departments in the university that makes their own policy, in which some documents are taken from the students and doesn’t give any proof that a certain document was duly received unless you ask one. I have observed this scenario last summer S.Y 2009-10. For what I have experienced when I enrolled for freshmen all original documents are endorsed ONLY in the office of the registrar.

However, as a whole the enrollment process is good for every year there are changes made into the process of enrollment which makes it more systematic compared with the last implementation. Like in enrollment of S.Y 2008-2009, once a student submitted his requirements he will be advices to wait until his name is called which is not ideal at all. However, for the succeeding year of implementation of the enrollment, the registrar initiated to have a window to cater transactions per college, the process still causes long queue since only 1 officer who receiver transactions per college, good for those colleges with lesser number of students compared to colleges with large number of students. And in the S.Y. 2009-2010 until this semester the registrar’s office initiated to make all transaction windows open to mall departments, apparently in improves the process of enrollment.

As year goes by, the enrollment process will really improve and will continue to improve to cater students effectively, however, even how structured or systematic the processes are, still the cooperation of the students and the people governing the school is what really matters. Students have to be vocal what’s in and right for the process; and for the governing people to be considerate and to look after everybody’s needs.


MIS 2 Assignment 7: All about GOOGLE

{ Posted on 3:48 PM by Ariel Serenado }
No comments
Google: The perfect search engine (Larry Page)

Nowadays, people of different places in different organizations are aware on the popularity marked by Google as a search engine. People find Google a convenient way to find a vast of information and ideas in different field of interest. Google paved the way for many organizations especially in the field of advertising. Google marked the highest revenue compared to its major and minor competitors all over the world. In search engine optimization it is always an ideal objective to give convenience in looking for a subject or a set of information in a very large resource. A good way to get many users in the search engine is making it really easy to use Google believes they should hide the complexity of their powerful and effective search engine from the followers so that they will be left with a simple, understandable way to get information they need. Google really does provide the best user experience possible, it refuses to make or deliver changes that would not benefit the users that go to their site. Google is a global technology leader focused in improving the ways people find and use information. Google maintain the world’s largest index of websites and other content and, via their automated search technology, make this information freely available, nearly instantly, to anyone with an internet connection.

Google is not just a popular search engine but also a business. Besides trying its best to satisfy its users it has to find way generating the most revenue. Google does this in a few different ways. The first one is the advertising which is the main source of the revenue that Google is getting from the advertisers, a program called AdWords paved for this business transaction thus, earning a high revenue among its competitors. A business using AdWords can accomplish greater cost effectiveness with their marketing budgets. AdWords is serving ads to thousands of third party websites who are part of the Google Network, this only means that advertisers using AdWords can target people by way of developing sites that are most likely be adapted by the people. The second way is offering its search technology, a program called AdSense paved for this particular business transaction. AdSense brings related texts, images, advertisements which are relevant to the content of your website. When a Google search box is added to your website, AdSense will deliver text ads which will go with the results of the visitors of the site, it also offers customization services. Thus, AdSense is not only maximizing the usability of the sites but also optimizes the operation. The third way is making money through Google Search Appliance which they sell to their customers. This transaction is very essential, especially that it delivers accurate search results throughout a number of documents. Meaning if the company will engage into Google Search Appliance, they will have its own search engine that works similarly with google.com. Thus, it gives the company’s employees, partners and customers the same quality that Google does.

The business model of Google comprises three models includes, Customer Model, Value Model and the Revenue Model. Three underlying models relate to the business approaches and offerings by Google. Like in the case of the value model, it involves search and community. It actually defines the search technology that Google is offering to its constituents and the community that embraces the said technology. Revenue model involves search services, advertising, it clearly defines the core offerings of the Google which is the search engine service and the main source of their revenue, Advertising.

Google has two types of competitors, the major and the minor competitors. Major competitors are Yahoo! Inc. and the Microsoft Corporation. The minor ones are American Online (AOL) and Baidu. Yahoo owns the world’s most popular websites and believes in multidimensional approach, wherein they identify what people want and out of it they can create a product that best suit to their clients’ needs. Google on the on the other hand owns the world’s leading online search engine, its mission it to transform the today’s world in storing or finding information. American online is an ISP or Internet Service Provider, in which subscribers nowadays are shrinking because of the development of broad band network technology. Baidu on the other hand is a Chinese search engine. It claims the biggest search engine in Chinese Language, the most popular feature of the search engine id to support MP3 search.

Furthermore, Google provides inclusion and frequent updating in their sites for free. Meaning anybody’s website could be in search results as possible. The unique about Google is that it uses the Pagerank technology as a result it makes the search result completely accurate. Google has worked very hard on getting rid of excess bit or byte from their pages to make it go as fast as it possibly can. Google developed new algorithms which proved that there was no limit as to how fast you could go in searching the most relevant information. Google’s services include Alerts where you receive news, Blog Search, which finds on people’s topics; Book Search; Images; Maps, where you find directions anywhere in the world; News. Some on the Google’s tools are Blogger, where you make express ideas online; Earth, lets you discover the world over your PC; Translate, view pages in other languages. Furthermore, Google has also a web browser built for speed, stability and security.

Larry Page: Google would understand exactly what you mean and give back what you want.

References:

http://scenariothinking.org/wiki/index.php/What_is_Google's_business_model?
http://www.google.com/intl/en/options/
http://investor.google.com/faq.html
http://www.seobook.com/archives/000273.shtml

SAD 1 Assignment 6

{ Posted on 3:43 PM by Ariel Serenado }
No comments
Juan: The way to go about the analysis is to first examine the old system, such as reviewing key documents and observing the workers perform their tasks. Then we can determine which aspects are working well and which should be preserved.

Pedro: We have been through these types of projects before and what always ends up happening is that we do not get the new system we are promised; we get a modified version of the old system.

Juan: Well, I can assure you that will not happen this time. We just want a thorough understanding of what is working well and what isn’t.

Pedro: I would feel much more comfortable if we first started with a list of our requirements. We should spend some time up-front determining exactly what we want the system to do for my department. Then you systems people can come in and determine what portions to salvage if you wish. Just don’t constrain us to the old system.

Insights...

The scenario is very common to those who are involved in technical aspect on system analysis. In this kind of scenario, adjustment is very important especially that you cannot expect everyone to make believe with the idea that you brought to the group. And you cannot force the people around you to implement the said idea or the approach because they do have their own perspective on how the process should be and how a system should be developed. This case is very crucial in a technical environment, there are many approaches, set of standards and with these standards there are corresponding processes and the worst case is that it is not flexible for some point, one have to consider an approach that the system is suited to. Considering now the fact that the two people involved in the presented scenario are not of the same field; from the situation we can somehow say that John Juan is a system analyst or project manager, and IT professional while Pedro Peter is most likely a department manager of a certain business company. It cannot be expected that these two people can immediately unify there ideas considering that their nature of work is different. There are related works that the system professional can relate towards the work of a department manager and so with the manager, there are task perform by system professional that he cannot relate to. Generally, people of different organizations have different outlooks in most processes these people take.

Going back to the scenario, let us first tackle the point made by the system professional, John Juan. A system professional has a wide range of idea in system analysis and developing systems that their clients want them to do, a system professional has a wide range of knowledge on how a project must be processed as to the stages and phases of development; therefore a system professional has the edge on the targeted system by the department manager. I got the point of John which is to examine first the old system that the company is using, review related documents, and observing the functionalities of the system. Knowing that not all developers has the knowledge on the operations of different organizations, so the manner of examining the old system paved the way for the system professional to evaluate and examine the functionalities of the old system, for him also to know how these functionalities relate to the day-to-day operations of the department. Also, the system professional can assess whether to make another system or maybe make some enhancement from the old system without compromising the functionalities of the system. Besides, developer can assess further which data of the involved system can be salvaged and can be migrated to the new system to be developed, otherwise the system professional will develop the required system “from scratch” which is most likely cumbersome to the developer or maybe to the developing team. This is also to reduce the time allotted for the system, instead of developing from the beginning; the developer can just make some improvements or maybe enhancements to realize the system in the least possible time.

Sometimes, it is not ideal for a developer to make another system without having examined the old system, for in developing system one has to have the initiative to utilize available resources before re-inventing tools and approaches. Furthermore, to just examine the old system is not sufficient to define some requirements towards the new system to be developed. The developer should engage a thorough investigation of the current system before defining requirements and specifications for the next system. Thorough investigation may involve interviewing the management and the operational staff, also by direct observation and experience on the system. A set of requirements and specifications, this means the additional functionalities that the new system needs, interfaces, etc.; performance standards, this means levels of system service in terms of quantity, quality, efficiency, effectiveness of the new system; social and technical requirements, this involves system architecture, architectural designs, the languages that the developer will utilize to capture the need of the client. However, the most critical thing in this stage is the knowledge of the end user or the intended user of the system and the effective interpretation of their needs by the developer or the system professional who deals all of these processes. Achieving correct interpretation requires the end user interest and values, and making amicable resolutions which largely meets the interest of both parties.

Pedro on the other hand has also the point which is to have requirements phase, specification analysis before they examine what portion of the system to salvage if they wish. To develop a system, one cannot jump directly to hard coding of the system, the development involves series of documentation to be done prior an implementation phase is made. Pedro mentioned listing of requirements; it is actually the very first phase in the life cycle of a system which covers 2% of the whole development. This phase’ goal is to explore and refine the concept of the system, as result requirements are being elicited. Moreover, in this phase the client outlines the product as he conceptualizes it. From the viewpoint of the developer, the client’s description of the desired product may be vague, unreasonable, contradictory, or simply impossible to achieve. The task of the task of the developer at this stage is to determine exactly what the client needs and to find out from the client what constraints exist. The second thing to do as what Pedro mean in his statement is Specification (analysis) phase, which cover 5% of the total development of the project. This phase is sometimes called “analysis phase”. At the end of this phase, a plan is drawn, the Software Project Management Plan (SPMP), describing the project in detail. Besides, the document includes the functional requirements. In this manner there is a formal project requirements elicitation close-out, requirements set by the client are finalized in the paper. Since there is a close-out if there are changes of the functionalities in the middle of the development then it should de dealt accordingly. In this manner also, you can formalize the functional requirements of the project so the developer can assess how the system should work an in times of examining the old system the developer can see which data, related functionalities will be saved. The idea can be of help to the developer since they will no be working the system “from a scratch”, instead they can make some enhancement for they already know the requirements that has been elicited prior the examination.

Software professionals are also human and therefore sometimes make error especially if requirements needed are not clearly defined. As a result, there will be fault in the system. If the error is made during the requirement phase, then the resulting fault probably will appear in the specifications, design, and most probably in the code. Clearly, the earlier we correct the error, the better. Because if the client discover fault later if the product has been delivered and deployed, cost may be another issue between the developer and to the client. Furthermore, sometimes you don not have to constrain yourself in old systems because not all system can be intermingled with the other program in the sense that some data cannot be migrated to the other system might be that they are using different technology. Also, the old system is not capable to work and cater the need of the client if intermingled with the new system. However, according to Stephen Schach, “up to now, everything seems to be straightforward. Unfortunately, the requirements elicitation phase is inadequately performed”. Reasons may include, the client may not truly understand what is going on in the organization, the client cannot clearly define the functional requirements that involve the operations in the organization. It is therefore hard for a developer to visualize the project when the client himself is not clearly defining the project as to the functional and non-functional requirements of the system. If that is the case then prototyping can be used until such the client is satisfied that the developer has finally captured the system they desired.

In my own notion, I would like to propose the idea of Pedro Peter. Ideally, Pedro is following the ideal stages that a system should undergo prior any implementation is being made. A system should undergo, a hard copy or the technical paper for the developer to finalize what is to develop and what is not.

SAD 1 Assignment 5

{ Posted on 9:01 PM by Ariel Serenado }
No comments

Consider your school, how do you know that the life cycle was developed specifically for the university. How do we know it meets our needs?

Systems Development Models are also referred as process models. In recent times, process models paved the way for the process of some projects involving information system implementation. The process models are typically used in structured analysis and design methods. The term process models are processes that are classified into a model. Thus, a process model is a description of a process. The same process is being used in repeatedly for the development of many applications and thus, has many instantiations. One possible use of a process model is to prescribe how things should be done as the process along through the documentation and finally into the development of the system or the project; also it is an anticipation of how process should look like. What the process shall be will be determined during actual system development. Moreover, process models are not interchangeable since, the output of the first phase is the input of the succeeding phase. To deliver a quality system, it is critical to know the risks facing your project and to use a model that reduces those risks. The following describes standard project lifecycle models, and reviews their strengths and weaknesses. These standard models can be adapted to fit the industry issues, corporate culture, time constraints and team vulnerabilities which comprise your environment. The lifecycle model is a Process Model; however, there are many kinds of lifecycle models that use different strategies for building software. Your choice of lifecycle model should be based on how a particular model will work in your environment, or for a specific project; e.g. factors that affect choice of lifecycle model include how constrained the project schedule is, how well-known the requirements are, how sophisticated the team is, etc. Your ability to choose the most appropriate model requires that you know several models and the pros and cons of each: a particular model's effectiveness depends on the context in which it is used (McConnell 1996, p. 154).

In this assignment, it talks about the System Development Life Cycle. SDLC is essentially a project management tool used to execute, plan, and control systems development projects. It is a systematic and orderly approach to solve problems. Furthermore, The Systems Development Life Cycle (SDLC), or Software Development Life Cycle in systems engineering and software engineering, is the process of creating or altering systems, and the models and methodologies that people use to develop these systems. The concept generally refers to computer or information systems.

This System Development Life Cycle involves the following general steps:

Planning. Identify the scope and boundary of the problem, and plan the development strategy and goals.

Analysis. Study and analyze the problems, causes, and effects. Then, identify and analyze the requirements that must be fulfilled by any successful solutions.

Design. Designing the solutions, of course in accordance to the problem that has been identified.

Implementation. The stage to apply all the necessary implementation to the project that is going to implement.

Support. Analyze the implemented solution, refine the design and implement improvements to te solution.

Going back to the question, in validating if the life cycle is designed specifically for the university, one has to consider the goals, mission, and vision of the school; to merely know if the cycle relates to the specific goals specified by the university. So that, in the long run of the projects, all things will be motivated not to go beyond the needs of the school. All things will be on the right track as the development process goes along.

Considering University of Southeastern Philippines…

The school has the following VMGO…

Mission

USEP shall produce world-class graduates and relevant research and extension through quality education and sustainable resource management. Particularly, USEP is committed to: Provide quality education for students to grow in knowledge, promote their well-rounded development, and make them globally competitive in the world of work; Engage in high impact research, not only for knowledge’s sake, but also for its practical benefits to society; and, Promote entrepreneurship and industry collaboration.


Vision

A PREMIER UNIVERSITY IN THE ASEAN REGION. By becoming a premier university in the ASEAN Region, the USEP shall be a center of excellence and development, responsive and adaptive to fast-changing environments. USEP shall also be known as the leading university in the country that fosters innovation and applies knowledge to create value towards social, economic, and technological developments.

Goals

Aligned with the university’s vision and mission are specific goals for Key Result Areas (KRA) on Instruction; Research, Development, and Extension; and Resource Management


KRA 1. Instruction
Produce globally competitive and morally upright graduates

KRA 2. Research, Development, and Extension (RDE)

Develop a strong R,D,&E culture with competent human resource and responsive and relevant researches that are adopted and utilized for development

KRA 3. Resource Management.

Now, how do we know if the cycle meets the needs of the university?

To merely know that every stage or phase of a certain cycle meets the cycle, in every end of the specific stage one must consider checking if certain goals were realized or if not, maybe some enhancements will be made to satisfy the needs of the university. What is visible in the environment now, is we do not monitor development in every end of a certain stage; instead we do it as the cycle ends. We must have the so-called, DEVELOPMENT MONITORING. T o keep track with the project enhancement projection must be observed. Any progress should be made recognize. Updates and improvements must also be identified and evaluated if it has been going well with what has been bad. Monitoring is an important part for the development. Proper monitoring has get different advantages like you must know the development of the performance.


Resources:

http://en.wikipedia.org/wiki/Systems_Development_Life_Cycle

http://www.usep.edu.ph/version/pages.php?m=50&id=24&pg=static&ntitle=ABOUT%20USEP

SAD Assignment 4: Systems Developemnt Models

{ Posted on 1:57 PM by Ariel Serenado }
No comments
Identify and discuss at least 3 systems development models …discuss each phase...

Systems Development Models are also referred as process models. In recent times, process models paved the way for the process of some projects involving information system implementation. The process models are typically used in structured analysis and design methods. The term process models are processes that are classified into a model. Thus, a process model is a description of a process. The same process is being used in repeatedly for the development of many applications and thus, has many instantiations. One possible use of a process model is to prescribe how things should be done as the process along through the documentation and finally into the development of the system or the project; also it is an anticipation of how process should look like. What the process shall be will be determined during actual system development. Moreover, the process model is typically used in structured analysis and design methods. Also, called a data flow diagram (DFD), it shows the flow of information through a system. Each process transforms input to outputs. Moreover, process models are not interchangeable since, the output of the first phase is the input of the succeeding phase. To deliver a quality system, it is critical to know the risks facing your project and to use a model that reduces those risks. The following describes standard project lifecycle models, and reviews their strengths and weaknesses. These standard models can be adapted to fit the industry issues, corporate culture, time constraints and team vulnerabilities which comprise your environment. The lifecycle model is a Process Model, however, there are many kinds of lifecycle models that use different strategies for building software. Your choice of lifecycle model should be based on how a particular model will work in your environment, or for a specific project; e.g. factors that affect choice of lifecycle model include how constrained the project schedule is, how well-known the requirements are, how sophisticated the team is, etc. Your ability to choose the most appropriate model requires that you know several models and the pros and cons of each: a particular model's effectiveness depends on the context in which it is used (McConnell 1996, p. 154).

To begin this assignment, there is a hundred of system development life cycle or what is also referred as process models. Some models do really have the same phases it differs only in the number of iterations, flexibility, and the approach to the system being developed. The following are the traditional and recently used systems development models or process models with strengths and weaknesses.

• Pure Waterfall
• Modified Waterfall
• Spiral
• Agile Software Development
• Extreme Programming

• Joint Application Development
• Design-to-Tools
• Rapid Application Development
• Scrum

Of all the process models, waterfall lifecycle is the most traditional of them all. This model has a top-down, or linear ordering to it. Normally, no phase is repeated, however, there may be overlapping between the different phases if necessary. Generally, the output of each stage is the input for the next. Waterfall has two types – pure waterfall and the modified waterfall.

Pure Waterfall

This is the classical system development model. It consists of discontinuous phases – Concept, Requirements, Architectural design, detailed design, Coding and Development, Testing and the Implementation. This kind of model works effectively to those projects with well defined and understood system requirements or in well understood technical tools. In general, its weakness is that pure waterfall is not advisable if rapid application is needle.

Strength: Structure lessens wasted effort, so it is convenient to those who are technically weak
Weakness: Not Flexible, the process should not be done up front.

Modified Waterfall

The modified waterfall use the same phases as the pure waterfall, but it is not done for a discontinuous basis. This enables the phases to overlap when added. This kind of model can split into subprojects at an appropriate phase. Flexible – risk reduction spirals can be added to the top of the waterfall to reduce risk prior to the waterfall phases. The model can be further modified using options as prototyping, JAD sessions or methods of requirements gathering done in overlapping places. Unforeseen interdependencies can create problems.

Spiral

This kind of model differs from waterfall cycle in terms of the linear approach. Some phases in the spiral are done repeatedly – phases such as planning, development, construction, and evaluation iterated until the development is done.

Strengths: The iterations enable the highest risks to be addresses at the lowest total cost. It is assumed that as the cost increases, risk decreases.
Weaknesses: It is complicated thus, requires attentive and knowledgeable management.

Agile Software Development

Agile methods generally promote a disciplined project management process that encourages frequent inspection and adaptation. It also refers to a group of software development methodologies based on the iterative development, where requirements and solutions evolve through collaboration between self organizing cross-functional teams.

Strengths: Minimizes feature creep by developing in short intervals resulting in miniature software projects mini-increments.
Weaknesses: Short iteration may not add enough functionality, leading to significant delays in final in final iterations. Agile method produces very little written documentation.

Extreme Programming

Extreme programming lowers the cost of changes through quick spirals of new requirements. However, programmers engaged in extreme programming are required to work in pairs which may be difficult for some developers which may result in more redesign effort in the long run.

Scrum

Is an iterative incremental framework for managing complex work, this is commonly used with agile software development. Although Scrum was intended for management of software development projects, it can be used to run software maintenance teams, or as s general project/program management approach.

Strength: The model allows you to prioritize work, completing items in a series of short iterations or sprints, daily measured progress and communication
Weaknesses: Its reliance o project teams and rejection of the traditional centralized process control may paralyze the team.

Evolutionary Prototyping

This model involves heavy user involvement while developers generate functional requirements and physical design specifications simultaneously. This model uses a lot of iterations; after each iteration, the result is analyzed by the customer. The response creates the next level of requirements an defines the next iteration.

Strength: The customer can see progress and can have the development monitoring. Useful when requirements are changing rapidly, when the customer is reluctant to a set of requirements.
Weaknesses: There is no way to know how much iteration to make. It is possible to know how long the project will take.

Rapid Application Development

This model focuses on building applications in a very short amount of time with comprise in usability, features, and/or execution speed. The emphasis on speed helps ensure that the client’ system requirements will not change as the process of development will start.

Strengths: Promotes strong collaboration and dynamic gathering of requirements. Clients are actively participating in prototyping, writing test cases and performing unit testing. RAD have the potential for providing a good framework for faster product development with enhanced code quality, but successful implementation and benefits often hinge on project type, schedule, software release and corporate culture.
Weaknesses: Dependency on cohesive teams and individual commitment to the project. Decision
making relies on the feature functionality.

Code and fix

If you don’t use methodology, it is likely you are doing code and fix. Code and fix rarely produces useful results. It is very dangerous as there is no way to assess progress, quality or risk.

Strengths: No time spent on overhead planning, documentation, quality assurance, standards enforcement or other non-coding activities.
Weaknesses: Fundamental flaws in approach do not show up quickly, often requiring work to be thrown out

Now, let’s discuss phases of some models.

waterfall model


The waterfall model is a sequential software development process, in which progress is seen as flowing steadily downwards (like a waterfall) through the phases of Conception, Initiation, Analysis, Design (validation), Construction, Testing and maintenance.

Feasibility

The feasibility study is used to determine if the project should get the go-ahead. If the project is to proceed, the feasibility study will produce a project plan and budget estimates for the future stages of development.

Requirement Analysis and Design

Analysis gathers the requirements for the system. This stage includes a detailed study of the business needs of the organization. Options for changing the business process may be considered. Design focuses on high level design like, what programs are needed and how are they going to interact, low-level design (how the individual programs are going to work), interface design (what are the interfaces going to look like) and data design (what data will be required). During these phases, the software's overall structure is defined. Analysis and Design are very crucial in the whole development cycle. Any glitch in the design phase could be very expensive to solve in the later stage of the software development. Much care is taken during this phase. The logical system of the product is developed in this phase.

Implementation

In this phase the designs are translated into code. Computer programs are written using a conventional programming language or an application generator. Programming tools like Compilers, Interpreters, Debuggers are used to generate the code. Different high level programming languages like C, C , Pascal, Java are used for coding. With respect to the type of application, the right programming language is chosen.

Testing

In this phase the system is tested. Normally programs are written as a series of individual modules, these subject to separate and detailed test. The system is then tested as a whole. The separate modules are brought together and tested as a complete system. The system is tested to ensure that interfaces between modules work (integration testing), the system works on the intended platform and with the expected volume of data (volume testing) and that the system does what the user requires (acceptance/beta testing).

Maintenance

Inevitably the system will need maintenance. Software will definitely undergo change once it is delivered to the customer. There are many reasons for the change. Change could happen because of some unexpected input values into the system. In addition, the changes in the system could directly affect the software operations. The software should be developed to accommodate changes that could happen during the post implementation period. You need to keep up with the project. In part this does mean that you should watch for bugs and other errors that are reported to you, and fix them. Yes, even your extensive testing regime may well have missed the odd issue here and there!

Just as importantly, though, is to keep developing the project. New ideas, new improvements, and simply bringing things up to date with the changing world (new currency for example!) are just as important to maintaining a project. Software and websites rarely need to die, as long as they are maintained. Look at everything from Windows to the Yahoo! website - the key to their longevity is that they are constantly renewed and updated. Keep the project fresh, relevant and useful, and it will survive.

Scrum Methodology


It is a practice-based methodology for modeling and documentation of software-based systems. It is intended to be a collection of values, principles, and practices for modeling software that can be applied on a software development project in a more flexible manner than traditional modeling methods. The system development process is complicated and complex. Therefore maximum flexibility and appropriate control is required. Evolution favors those that operate with maximum exposure to environmental change and have optimized for flexible adaptation to change. Evolution deselects those who have insulated themselves from environmental change and have minimized chaos and complexity in their environment. An approach is needed that enables development teams to operate adaptively within a complex environment using imprecise processes. Complex system development occurs under rapidly changing circumstances. Producing orderly systems under chaotic circumstances requires maximum flexibility. The closer the development team operates to the edge of chaos, while still maintaining order, the more competitive and useful the resulting system will be. Langton has modeled this effect in computer simulations13 and his work has provided this as a fundamental theorem in complexity theory.

Characteristics of SCRUM methodology are:

• The first and last phases (Planning and Closure) consist of defined processes, where all processes, inputs and outputs are well defined. The knowledge of how to do these processes is explicit. The flow is linear, with some iteration in the planning phase.
• The Sprint phase is an empirical process. Many of the processes in the sprint phase are unidentified or uncontrolled. It is treated as a black box that requires external controls. Accordingly, controls, including risk management, are put on each iteration of the Sprint phase to avoid chaos while maximizing flexibility.
• Sprints are nonlinear and flexible. Where available, explicit process knowledge is used; otherwise tacit knowledge and trial and error is used to build process knowledge. Sprints are used to evolve the final product.
• The project is open to the environment until the Closure phase. The deliverable can be changed at any time during the Planning and Sprint phases of the project. The project remains open to environmental complexity, including competitive, time, quality, and financial pressures, throughout these phases.

SCRUM has the following groups of phases:

Pregame
• Planning : Definition of a new release based on currently known backlog, along with
an estimate of its schedule and cost. If a new system is being developed, this phase
consists of both conceptualization and analysis. If an existing system is being
enhanced, this phase consists of limited analysis.
• Architecture : Design how the backlog items will be implemented. This phase
includes system architecture modification and high level design.
Game
• Development Sprints : Development of new release functionality, with constant
respect to the variables of time, requirements, quality, cost, and competition.
Interaction with these variables defines the end of this phase. There are multiple,
iterative development sprints, or cycles, that are used to evolve the system.

Postgame
Closure : Preparation for release, including final documentation, pre-release staged
testing, and release.

Phase Steps

Each of the phases has the following steps:
Planning
• Development of a comprehensive backlog list.
• Definition of the delivery date and functionality of one or more releases.
• Selection of the release most appropriate for immediate development.
• Mapping of product packets (objects) for backlog items in the selected release.
• Definition of project team(s) for the building of the new release.
• Assessment of risk and appropriate risk controls.
• Review and possible adjustment of backlog items and packets.
• Validation or reselection of development tools and infrastructure.
• Estimation of release cost, including development, collateral material, marketing,
training, and rollout.
• Verification of management approval and funding.
Architecture/High Level Design
• Review assigned backlog items.
• Identify changes necessary to implement backlog items.
• Perform domain analysis to the extent required to build, enhance, or update the
domain models to reflect the new system context and requirements.
• Refine the system architecture to support the new context and requirements.
• Identify any problems or issues in developing or implementing the changes
• Design review meeting, each team presenting approach and changes to implement
each backlog item. Reassign changes as required.
Closure
When the management team feels that the variables of time, competition, requirements, cost, and quality concur for a new release to occur, they declare the release “closed” and enter this phase. This phase prepares the developed product for general release. Integration, system test, user documentation, training material preparation, and marketing material preparation are among closure tasks.

Rapid Application Development (RAD)


Rapid Application Development (RAD) refers to a type of software development methodology that uses minimal planning in favor of rapid prototyping. The "planning" of software developed using RAD is interleaved with writing the software itself. The lack of extensive pre-planning generally allows software to be written much faster, and makes it easier to change requirements
Below is a brief overview of the RAD process, which consists of four lifecycle stages: Requirements Planning, User Design, Construction, and Implementation. Also described are typical pre and post project activities.

The Gantthead project management portal is an excellent resource that contains more far more details on the process and additionally contains sample project plans and details on techniques such as time boxing, project estimation, recommended tools, and work breakdown structures. Do not begin your project without at least looking at this vital resource. Additional information is also available on the slightly dated but otherwise excellent website put together by Walter Maner of Bowling Green State University.

Pre-Project Activities

As with any project it is vital to identify the details of the project up front in some form of document such as a Project Management Plan (PMP). All parties should agree up front on details such as potential risks and mitigation strategies, a development schedule including resources, milestones and deliverables such as a completed data model or types of documentation to deliver, an approach including standards, tools, and technologies to be used, a desired end result, terms and constraints and financial considerations including budget and cost of tools.

Requirements Planning

The Requirements Planning stage (also known as the Concept Definition Stage) consists of meetings between a requirements planning team and key client users. Meetings focus on both developing a high level list of initial requirements as well as setting the project scope. The requirements planning team identifies primary business functions (such as "sell widgets to the Acme corporation") and initially breaks them down into business entities (such as Product, Sale, Company, Sales Person). The Requirements Planning stage should result in a list of entities as well as action diagrams that define the interactions between processes and data elements and should take between one and four weeks. Ideally requirements should be captured in a structured tool such as IBM's Rational Rose or Rational RequisitePro or Microsoft's Visio (the enterprise edition, since it can generate databases from a data model) rather than an unstructured document (see the tools section below for more details). At the end of the Requirements Planning stage project estimation should be considered. The International Function Point Users Group as well as the International Software Benchmarking Standards Group offer project estimation methods based on "function points" along with a vast database of actual projects with the effort involved to complete them.

User Design

During the User Design stage (also known as the Functional Design Stage) the analysis team meets with end users in Joint Application Development (JAD) Workshops. During the workshops the analysis team flushes out the requirements in more detail, develops the entities developed in the Requirements Planning into a data model (Entity Relationship Diagram), formalizes business rules, develops test plans, and creates screen flows and layouts for essential parts of the system. During the later half of the User Design stage the development team (also known as the SWAT or Skilled Workers with Advanced Tools team) aids the analysis team in activities such as creating a working data model that can be converted to a functional database, and in identifying reusable components (such as Microsoft's Application Blocks, which, incidentally, are an excellent time saver on Microsoft .Net projects). Again, as mentioned in the Requirements Planning stage, all requirements should be captured in a tool.

Before moving to the Construction Stage the analysis team should focus on next steps by flushing out the project plan and focusing on effort estimates. Focusing on next steps is an important element of the User Design phase, because the initial iteration of the Construction Phase should focus on a feature light prototype. In order to keep development iterations as short as possible, and to gain the maximum benefit of RAD's agile nature, core requirements should be identified and targeted for the initial prototype, and secondary requirements should be identified and targeted for future development iterations. Beyond a vertical limiting of scope, such as removing entities or use cases from the initial scope, a horizontal type limiting of scope should be considered as well, such as not developing field validation, not developing file upload/download capabilities, or focusing on just the strengths of the particular CASE tool being used without manually adding much developer customization.

The User Design stage should last between three and five weeks.

Construction

During the Construction Phase the Design Team develops the application in iterative cycles of development, testing, requirements refining, and development again, until the application is complete. Development iterations should last between one day and three weeks. The development team should convert the Data Model that was developed during the User Design Stage into a functional database (all data modeling tools have this ability). The CASE tool used (which may be the same as the data modeler or a separate tool) should now generate large sections of the application, at a minimum data access code, but preferably business functions and user interface as well.

At Automated Architecture, our Blue Ink product will read information from database that has been generated, pre-generate answers to meta-data about the project (in other words make a best guess as to the details of your application that you may then customize in more detail later), and generate an entire application that can serve as a working prototype without a line of development code. A prototype developed in this way may reduce the first iteration of development to days instead of weeks.

It is vital to keep each development iteration on track, and functionality may need to be dropped to keep development within the time box. Management plays a vital part in ensuring everything is progressing according to schedule, keeping the customer in the loop regarding changes in the functionality, and keeping the team motivated.
Once the prototype has been developed (within its time box), the construction team tests the initial prototype using test scripts developed during the User Design stage, the design team reviews the application, the customer reviews the application and finally the construction team, design team, and customer meet in Focus Group meetings in order to determine the requirements for the next iteration. Focus group meetings consist of facilitated sessions that last about two hours. The facilitator should know ahead of time the areas that require discussion and should ensure that each issue receives enough attention, keeping a list of issues that require additional attention in a separate meeting as appropriate.

After the meeting (additional meetings may be necessary), the development team and design team should update the requirements, data model, test scripts, and project plan as during the User Design stage. Again the teams should identify core and secondary requirements, plan out the next development iteration, keep the user in the loop regarding what will be done, and then start the next iteration of development over again. As the system approaches a sufficient state the development team should focus on the system as a finished application rather than a prototype.
During the final iterations of development the design team should update user documentation, perform User Acceptance Testing and define the steps necessary for deployment/implementation.

Implementation

The Implementation Stage (also known as the Deployment Stage) consists of integrating the new system into the business. The Development Team prepares data (such as lookup values like States and Countries) and implements interfaces to other systems. The Design Team trains the system users while the users perform acceptance testing. and are trained by the Design Team. The Design Team helps the users transfer from their old procedures to new ones that involve the new system, trouble shoots after the deployment, and identifies and tracks potential enhancements (read wish list). The amount of time required to complete the Implementation Stage varies with the project.

Post-Project Activities

As with any project final deliverables should be handed over to the client and such activities should be performed that will benefit future projects. Specifically it is a best practice for a Project Manager to review and document project metrics, organize and store project assets such as reusable code components, Project Plan, Project Management Plan (PMP), and Test Plan. It is also a good practice to prepare a short lessons learned document.

References:

http://www.blueink.biz/RapidApplicationDevelopment.aspx
http://acmesoffware.com/acme/default.asp
http://www.startvbdotnet.com/sdlc/sdlc.aspx
http://jeffsutherland.com/oopsla/schwapub.pdf

SAD Assignment 3: Roles of a system analyst as s project manager

{ Posted on 1:55 PM by Ariel Serenado }
No comments
Discuss the role of a systems analyst as a project manager. You need to interview an analyst/project manager …

Actually, SYSTEM ANALYST AS A PROJECT MANAGER is our topic for the reporting in System Analysis and Design 1. Luckily, just one day before the schedule we did an interview with the system analyst of AMS Group of Companies. Unfortunately, the time did not permit us to share some information that our group gathered from the said interview since, the group was not able to finish their reports with sharing in the specified time. Our group is expected to have the reporting the first meeting next year.

System Analyst is responsible for researching, planning, coordinating and recommending software and system choices to meet an organization's business requirements. The systems analyst plays a vital role in the systems development process. A successful systems analyst must acquire four skills: analytical, technical, managerial, and interpersonal. Analytical skills enable systems analysts to understand the organization and its functions, which helps him/her to identify opportunities and to analyze and solve problems. Technical skills help systems analysts understand the potential and the limitations of information technology. The systems analyst must be able to work with various programming languages, operating systems, and computer hardware platforms. Management skills help systems analysts manage projects, resources, risk, and change. Interpersonal skills help systems analysts work with end users as well as with analysts, programmers, and other systems professionals.

Most systems analysts work with specific types of computer systems—for example, business, accounting, and financial systems or scientific and engineering systems—that vary with the kind of organization. Analysts who specialize in helping an organization select the proper system hardware and software are often called system architects or system designers. Analysts who specialize in developing and fine-tuning systems often have the more general title of systems analysts. A systems analyst designs new IT solutions to improve business efficiency and productivity. The work might be for an external client or an internal client (such as a department within the same organization). Working closely with the client, analysts examine existing business models and flows of data, discuss their findings with the client, and design an appropriate improved IT solution. They produce outline designs and costing of new IT systems, specifying the operations the system will perform, and the way data will be viewed by the user, present their design to the client and, once it is approved, work closely with the client team to implement the solution.

According to Mr. Gemrald, a system analyst who is more focused on system design and the technical aspects of the solution. The systems analyst’s role is mostly system solution centric and does not participate in the requirements gathering process and is involved in the creation of functional and technical specifications. In the system development life cycle, System Analyst is generally involved only in the first phase of the cycle, which includes system requirements gathering and specifications but of course, the system analyst has some task to get involved in some phases but as he mentioned that system analysts are generally involved only in the first and second phase of developing a cycle. Moreover, this is the professional who, once requirements are clearly defined, creates the functional solution and, by working with the technical team (architect and developers), creates technical specifications and designs. However, Mr. Gemrald is not just a system analyst he is also the project manager whenever they developed some systems that the company wants them to create, that is why in the long run of the cycle he is always involved up to the maintenance. One thing that Mr. Gemrald had told us is, “I’m not a one-man-team”. Furthermore, the team where he is in is not practicing project close-out whenever a phase has been finished; for they are working in-house for them it’s not that vital to practice so. That is only applicable to those analyst whore are engaged in outsourcing, he added.

Most common roles of System Analyst are the following:

1) System analysis
It includes system's study in order to get facts about business activity. It is about getting information and determining requirements. Here the responsibility includes only requirement determination, not the design of the system.
2) System analysis and design:
Here apart from the analysis work, Analyst is also responsible for the designing of the new system/application.
3) Systems analysis, design, and programming:
Here Analyst is also required to perform as a programmer, where he actually writes the code to implement the design of the proposed application. For Mr. Gemrald, he admit that the team really lacks programmers that is why there are really instances where he is into programming, hence it is one also of the nature of an analyst having the logical and analytical skills specifically programming skills.

Due to the various responsibilities that a system analyst requires to handle, he has to be multifaceted person with varied skills required at various stages of the life cycle. In addition to the technical know-how of the information system development a system analyst should also have the following knowledge.

• Business knowledge: As the analyst might have to develop any kind of a business system, he should be familiar with the general functioning of all kind of businesses. Mr. Gemrald noted that once you are a system analyst it is assumed that you know some aspects in business fields, especially to him that most of the system that his team is developing are enterprise systems, meaning it involves business-related transactions.
• Interpersonal skills: Such skills are required at various stages of development process for interacting with the users and extracting the requirements out of them. Of course, as s system analyst you need to be in connected with the client, you have to build common channel of communication between the developer and the user, to attain the specific requirement s that the uses need most.
• Problem solving skills: A system analyst should have enough problem solving skills for defining the alternate solutions to the system and also for the problems occurring at the various fields. It is vital to a system analyst to be flexible in terms of providing solutions in systems with various structures of data and information. For in programming, all things are subjective, you cannot just stick to a single programming language to provide solutions, there programming languages which cater built-in functionalities an more convenient to use.

References:
http://www.freetutes.com/systemanalysis/role-of-system-analyst.html
http://en.wikipedia.org/wiki/Systems_analyst

SAD 1 Assignment 2: Characteristics of a good system ananlyst to be more effective in any modeling process

{ Posted on 1:52 PM by Ariel Serenado }
No comments
“Interview a System Analyst and ask what skills and characteristics must a system analyst develop in order to be more effective in any design modeling process”

Last week’s meeting in System Analysis and Design our group should have reported the chapter 3 which is on “System Analyst as a Project Manager”. Unfortunately, the report by the 2nd group exceed in the required time to finish that’s why we were not able to deliver our report. To gather much information on our report we did interview the MIS Head/System Analyst of the Andres M. Soriano (AMS) Group of Companies, Mr. Gemrald Glibara.

In the interview, we talk mostly on becoming a system analyst, what are those frustrations towards the user and how they develop information systems. At some point in our interview, we asked him about the characteristics of being a system analyst; he made mentioned the following:
• To be able to cope with technological changes
• To cope with the frustrations on implementing information system
• To be able to communicate well
• Solution provider to the current demand
• Wide capacity of thinking

At some point also, we talked on the process model(s) that their department is utilizing in developing projects. Later will be discussed on the process that AMS is using.

Nowadays, technological advances come so rapidly in the computer field that continuous study is necessary to remain competitive. Employers, hardware and software vendors, colleges and universities, and private training institutions offer continuing education to help workers attain the latest skills. In this fast-paced technological environment, it is a must that an analyst has good knowledge of the concepts and details of the Systems Development Life Cycle, project methodologies, and the development of standards and procedures for the systems development and integration process.

What is a System Development Cycle (SDLC)?

The Systems Development Life Cycle (SDLC) is a conceptual model used in project management that describes the stages involved in an information system
development project from an initial feasibility study through maintenance of the completed application.

Various SDLC methodologies have been developed to guide the processes involved including the waterfall model (the original SDLC method), rapid application development (RAD), joint application development (JAD), the fountain model and the spiral model. Mostly, several models are combined into some sort of hybrid methodology. Documentation is crucial regardless of the type of model chosen or devised for any application, and is usually done in parallel with the development process. Some methods work better for specific types of projects, but in the final analysis, the most important factor for the success of a project may be how closely particular plan was followed.

What is the importance of SDLC?

The importance of using software development lifecycle is that it helps systems analyst to develop an information system in an organized way for, it has phases -- including requirements, validation, training, and user ownership through investigation, analysis, design, implementation, and maintenance. In developing project using SDLC you cannot jump into the next phase if the current phase you are working is not yet done for, in most cases the output of the first phase happened to be the input of the succeeding phase. That’s why for the documenter to feel at ease in documenting the project he/she must set timelines and work breakdown structures to manage each phases of the cycle effectively.

In order for an analyst to become effective in any design modeling process, he\she should acquire the following skills:

Interpersonal skills
These includes the following:

1: Communication:

It is an interpersonal quality; the system analyst must have command on English language. Communication is necessary to establish a proper relationship between system analyst and the user.
Communication is need to gather correct information.

2: Understanding:

This is also an interpersonal quality of the system analyst, understanding includes :
a. Understanding of the objectives of the organization.
b. Understanding the problems of the system.
c. Understanding the information given by the user or employee of the organization.

3: Selling:

The ideas of the system analyst are his products which he sells to the manager of a particular organization. The system analyst must have not only the ability of creating ideas but also to sell his ideas.

4: Teaching:

It is also an interpersonal quality. A system analyst must have teaching skills. He must have the ability to teach team members and the users. He has to teach about the new system and also about the proper use of the new system.

5: New technology:

An analyst is an agent of change, he or she must have the ability to show all the benefits of the candidate system with the new technological advancement, he must knew about.

Yes. Analyst is an agent of change, but how will an analyst cope up with the frustrations on implementing projects. In this scenario communication skills will really TEST the analyst on how will he manage the people who are considered “resistant to changes”. In any organization, you cannot expect that everyone is adaptive to the changes, some people think that the usual thing is the best but as you see the real scenario; technology changes from time to time, so the company should evolve by way of technological enhancement of advancement. This scenario is really happening to the AMS, some employees appear to be resistant to changes for some reasons.

Another list of skills that analyst must posses to be more effective in any design modeling process:

Analysis and Solution Definition Skills:

•To coordinate with Solution and Demand Management (SDM) team and different business users to manage business requirements and develop clear and workable high level assessments and Solution Design documents fulfilling business needs and in line with Technology and IT ability to deliver.
•To always drive and personally perform research and investigation in all relevant technology and business areas to ensure the Intranet presences is coping with industry standards.
•Translate requirements defined by business analyst into logical, economical and practical system designs.
•Analyzes and Designs system flow and procedures to ensure optimum control and security of data and efficient use of resources
•Develops functional specifications and system design specifications for client engagements.
•Work with vendors and service providers to analyze, design and implement robust, extensible and creative web solutions weighing costs versus benefits.
•Write high and detailed level business requirement documents
•Liaise with business users for requirements gathering, analysis and delivery
•Ensure proper development and implementation of projects by smartly decide on how to implement solutions by assessing all options of in-house development, out-sourcing and/or productized solutions

Technical Skills for Recommendation and Testing:

•Leads testing efforts.
•Ensures issues are identified, tracked, reported on and resolved in a timely manner.
•Works with client personnel to identify required changes.
•Communicates needed changes to development team.
Project Execution:
•Ensure that company’s policies and regulations are thoroughly followed in all projects. This includes but not limited to policies for procurement, vendor relations, legal, financial, human resources, customer service and technology.
•To ensure that the implemented solutions shall operate as planned by ensuring proper and comprehensive coordination with all IT and technology operation teams. This includes but not limited to planning and executions of SLAs, Training, Escalations Matrix & Procedures, Maintenance Windows, etc.
•Assists in enforcement of project deadlines and schedules.
•Takes input from supervisor and appropriately and accurately applies comments/feedback.
•Manages resources in accordance with project schedule.
•Consistently delivers high-quality services to our clients.
•Apply best-practices in Project Management to ensure robust project planning and monitor project execution, shorten the development cycles, and ensure on-time and on-budget delivery based on PMI Methodology
•Manage project change requests by liaising with CR department, business users and vendors to come up with the best solution that would accommodate the CR performance needs (scope, time, quality, cost and customer satisfaction)
•Ensure tight and close management to development and implementation teams including staff, contractors and vendors on-site and off-shore and to proactively avoid delay in the execution by proper follow-up, communication and escalation
•Manage teams including staff, contractors and vendors on-site and off-shore and to proactively avoid delay in the execution by proper follow-up, communication and escalation
•Monitor project performance and adherence deadlines to ensure delivery on time and within cost
•Collaborate and manage project stakeholders, manage expectations and report progress

Communication Skills:

•Assists in the facilitation of team and client meetings.
•Delivers informative, well-organized presentations.
•Understands how to communicate difficult/sensitive information tactfully.
•Communication and interpersonal skills, Ability to foster a co-operative work environment

Technical Understanding Skills:

•Possesses understanding in the areas of application programming, database and system design.
•Understands Internet, Intranet, Extranet and client/server architectures.
•Understands how legacy and web-based systems interface with each other.
•Architect technical web solutions in support of corporate IT/business objectives.
•Review technical designs & specifications and identify website or system deficiencies, and thereby recommending appropriate solutions.
•Support and maintain the existing corporate website and functionalities, including documentation of functional and systems specifications.
•To undertake research and investigation for all development related technologies, techniques, best-practices and forums.

Problem Solving Skills:

•Follow up the defects of the systems and prepare needed development/testing environments (SIT and UAT)
•Exhibits confidence and an extensive knowledge of emerging industry practices when solving business problems.
•Pushes creative thinking beyond the boundaries of existing industry practices and client mindsets.
•Ensure business requirements are met, and user satisfaction
•Process, validate and approve vendors’ invoices and purchase orders
•Monitor project performance and adherence to project plan execution, overall change control

Leadership and Teamwork Skills:

•Ensure that the implemented solutions shall operate as planned by ensuring proper and comprehensive coordination with all IT and technology operation teams as planned in SLAs
•Take proactive and corrective action as necessary and within established guidelines
•Proven leadership capability in managing teams, setting common ground rules and conflict resolution
•Able to support multiple projects concurrently and efficiently
•Acumen and awareness of the latest business and technologies thru research and development

Knowledge, Skills, Experience and Competencies:

•Software development skills
•Analysis & Design skills
•Communication skills
•Conflict Resolution skills
•Presentation skills
•Team Work & cooperation
•Can-Do Attitude
•Team Building & Coaching
•Customer-Centric Thinking
•Result Oriented
•Flexibility

As I remembered from the interviewee, his views on becoming a Systems analysts is that he/she must be able to think logically and have good communication skills, they often work in teams on large projects. They must be able to communicate effectively with computer personnel, such as programmers and managers, as well as with users or other staff who may have no technical computer background. In the part of our interviewee aside from he is working as the MIS Dep’t Head, he is also the System Analyst. However, they lack programmers in their department but he said he can do programming but it is very hard to be a “one-man-team”. Of course, analysts should be familiar with programming languages and have a broad knowledge of and experience with computer systems and technologies, strong problem-solving and analysis skills, and good interpersonal skills. AMS is a business-oriented company, that’s why it is a requirement for them to have background on business-related transactions and operations, especially that most of the systems that they are developing are enterprise systems.

One of the skills that an analyst must posses is the skill to choose the right process model depending on the mode of the project. In the part of AMS, RAPID APPLICATION DEVELOPMENT. This kind of process model requires less formality and minimal planning in favor of rapid prototyping. The lack of extensive pre-planning generally allows software to be written much faster, and makes it easier to change requirements. Mr. Gemrald and company discouraged to use WATERFALL METHOD, for they understand that what they are developing are enterprise systems, and the most common thing that happened developing enterprise system is that it overruns. They are comfortable to use the RAD process model. In my notion, for an analyst to chose the effective process model, he/she must have the "Analysis and Solution Definition
Skills", for this skills involves coordination with Solution and Demand Management (SDM) team and different
business users to manage business requirements and develop clear and workable
high level assessments and Solution Design documents fulfilling business needs
and in line with Technology and IT ability to deliver; which is very related to system development life cycle's phases.



References:

Justify Fullhttp://www.blurtit.com/q170760.html
http://www.gulftalent.com/home/Systems-Analyst-Microsoft-Net-Solutions-jobs-in-UAE-34448.html
Subscribe to: Posts (Atom)