Recent orders

Linux Is Hard To Rule The PC Operating Systems, But It Can Be Widely Used In The Area Of Server Systems And Embedded Systems

Linux Is Hard To Rule The PC Operating Systems, But It Can Be Widely Used In The Area Of Server Systems And Embedded Systems

Introduction

An increase in Linux applications for server and embedded system developments has generated an enthusiastic up-surge in embedded OS market. This aspect is contrasted to its relatively uncompetitive nature in PC and workstations field. WindRiver Systems (WRS) may be considered as a key provider embedded OS vendor, despite an attempt by Microsoft to enter the fray with its Windows CE (Compton, 2000).

It is a tricky effort to predict the future in PC, serve and embedded systems; often it has turned out to be a failed endeavor. In this paper most arguments will be based on positioning of traditional players in embedded systems as of present. Also several initiatives, trends, and forces driving Linux towards embedded systems will be covered. lastly, attention will be paid on how free software and open source community as well as developers of embedded systems influence choice of Linux as a leader in Operating systems (OS) (Yaghmour,2003).

Embedded OS systems

An embedded device refers to any internally sophisticated system comparable to a computer, but does not resemble the traditional desktop machine or serve. Examples range from the “Black box”, internet router, to touchy consumer devices such as credit card readers or cash registers (Lehrbaum, 2001).The universe of embedded computing encompasses PCs of different sizes scaling from portable tiny devices like wristwatch cameras to large systems having thousands of nodes such as telecommunication switches in mainstream worldwide distribution. Embedded systems range from simple microcontrollers to parallel and massive processors which are prodigious to computing memory power (Deshpande, 2004).

Linux operation system is not new, it has been available for years for desktops and servers and has continually gained market share for both computing segments. This growth lends credibility to Linux to established companies in PC industry such as Hewlett-Packard, IBM, Oracle, Dell, Compaq and others. Although Linux was primarily designed for desktop followed by adaptation to servers, it is currently a force to reckon after entering the fragmented embedded system market (Lehrbaum, 2001).

The embedded OS market still remains fragmented. However, the market tilted in favor of Linux long time when majority of engineers (50%) preferred “roll your own” operating systems which are in-house and custom-made. for this reason Linux becomes more attractive grabbing sizeable market from board established vendors of embedded OS. Linux has also capitalized on this aspect to penetrate the last frontier in global embedded OS. Jack Ganssle, however cautions that Linux future in embedded world is hazy (Yaghmour, 2003).

For instance, BlueCat Linux was released by Real-Time Systems (RTOS) in November 1999, which later changed name to LynuxWorks. Linux added LynxOS to run unmodified binaries for its proprietary RTOS. The company strategy was to capture market for royalty-free and non-real-time embedded OS which continues up to today through BlueCat and LynxOS. Linux is ahead of competitors because most of them like WRS and QNX failed to engage free software and open source community instead made grave mistake by spreading FUD or launching substitutes to please developers of embedded systems (Yaghmour,2003).

Subsequently, stability in Linux commercials has increased in numbers because it’s major distributors of have collapsed into a small but powerful group. This include, SuSE, Red Hat, Debian, mandrake, Slackware, others are Xandros, Gentoo, and LindowOS. The company has taken advantage of growth in Linux installation packages due to improved skills among people (Adam, 2003). For example, Linux release of Kernel 2.6 polarized competition to key vendors of RTOs, such as WinCE and VxWorks to capture a niche in embedded market. The Linux 2.6 introduced various new applications making it an excellent OS in embedded computing. Easier porting to new PCs, enhanced real-time performance, improved I/O, large memory models, and microcontroller’s support system features are reminiscence of Linux 2.6. The features of kernel 2.6 empowered it as a technology firm of choice in the embedded computing world (Deshpande, 2004).

Competition by Microsoft flopped twice in its quest to dominate the embedded market, first by introducing Windows CE which performed marginally, followed by Windows NT embedded system. Despite the competition, Linux still managed to scale heights by heaping a $ 3.5 billion per annum from embedded system development tools. In the past two years alone, enthusiasm for Linux systems has dramatically increased (Compton, 2000). Future of Linux looks bright with the launch of Mini-ITX as one of modern Ultra-compact technology targeting new generation entertainment and information systems. This technology has revolutionized latest generation minute, ergonomic, affordable, and innovative embedded systems incorporating technology convergence and integration such as Flash, Slim-drives and other potable gadgets (Linux Devices, 2004).

The merits that Linux offers in embedded systems are similarly applied its popular Server operating system strengths. This includes low cost, open source code, and high reliability. This is a plus for most programmers working on Linux OS development. Although, TimeSys and MontaVista as established embedded OS players leading claim for new markets targeting Linux distributors, their efforts can not surplus advantages of systems such as BlueCat and Lynux Real-Time Systems among their users (Compton, 2000).

Conclusion

Success of Linux in server and embedded systems unlike the PC competition is attributed to technology revolution amid economic, financial, and technological inhibitions without fear of unknown. Company’s which stick on the past and worry over risks limits management from venturing into future prosperity. Therefore Linux, embedded systems versatile compatibility simplified complex applications to satisfy human needs. Innovation of Mini-ITX is one of modern Ultra-compact technology targeting new generation entertainment and information systems. This technology has revolutionized latest generation minute, ergonomic, affordable, and innovative embedded systems incorporating technology convergence and integration (Linux Devices, 2004).This can be likened to delegating responsibility to vendors in the field, generating sound business economics, and increasing market share with aim of future long-term benefits (Heller, 2006).

References

Adam, S (2003). The Future of Linux. Retrieved August 16, 2010 from <http://www.osnews.com/story/5354/Editorial_The_Future_of_Linux>

Compton, J. (2000).Is Linux the Embedded Operating System of the Future? Retrieved August 16, 2010 from <http://www.developer.com/tech/article.php/625941/Is-Linux-the-Embedded-Operating-System-of-the-Future.htm>

Deshpande, A.R. (2004). Linux Kernel 2.6: the Future of Embedded Computing, Part I. Retrieved August 16, 2010 from <http://www.linuxjournal.com/article/7477>

Heller, R. (2006). Business Competition: The new challenges and challengers in the business revolution. Retrieved August 16, 2010 from <http://www.thinkingmanagers.com/management/business-competition.php>

Lehrbaum, R. (2001). Whitepaper: Linux’s Future in the Embedded Market. Retrieved August 16, 2010 from <http://www.linuxfordevices.com/c/a/News/Whitepaper-Linuxs-Future-in-the-Embedded-Market/>

Linux Devices. (2004). Mini-ITX madness. Retrieved August 16, 2010 from <http://www.linuxfordevices.com/c/a/Linux-For-Devices-Articles/MiniITX-madness/>

Yaghmour, K. (2003). Building Embedded Linux Systems: Embedded Systems, Linux, and the Future. Retrieved August 16, 2010 from <http://www.cotsjournalonline.com/articles/view/100129>

LINK UP SYSTEM. Workflow Analysis and Scheduling

LINK UP SYSTEM

Workflow Analysis and Scheduling

Documents Enclosed

Section 1Task/Result List3

Section 2 PERT Chart4

Section 3 Gantt Chart5

Section 4Scheduling Constraints 6

Section 5Risks Avoided by Schedule Choice7

Link Up

The project designed and described earlier in our project design and control assessment stage involves development and implementation of a new computer system for the Community Mental Health System to be implemented in 83 counties with in the state of Michigan and its partner agencies. The project will assist in improving mental health care in different ways especially in providing a direct line communication between agencies irrespective of their geographical locations. Since the project will involve providing a secure network, it will better coordination, efficiency and speed up authorization of services for mental health patients within the state. Proper filling and access of medical records play a huge role of improving health care and the secure network will provide a good platform for record keeping. Moreover, the billing through the new system will be faster as well as appraisal of the period required to provide services to a client. Faster and easier authorization of services is bound to better accountability and provision of similar health care within the counties. Link up will further be helpful in maintaining quality mental health by eliminating future briefs and reports in case of patient transfers within the agencies since all patient information will be available in the system and accessible by health practitioners within the state of Michigan.

Question 2

Task Result List

Tasks to be Completed

Time Est. Results

1 Conduct a meeting to identify the agencies as well as counties likely to be affected by the new system. .5 day Following the identification of the staff and organizations likely to be affected, the team will be able to determine the hardware, software and knowledge needs of these employees.

2 Site Coordinators and administrators trained and certified

5 days Site coordinators and other administrators, including myself, concerned with overall training and implementation of the program will be trained and knowledgeable on the scope

3 Counties and other agencies that require certain hardware and software upgrades prior to the implementation of the project engage in urgent procurement exercises. 10 days Counties as well as other concerned agencies will be prepared to adopt the new Link Up system.

4 Meet up with site managers to schedule training dates as well as divide the training groups and the trainers into two. .5 day The groups to be trained from the 83 counties will be divided into 16 groups, 2 to be trained simultaneous. As such, 8 rounds of training to be carried out simultaneously will be scheduled.

5 Management will post the training schedules online and direct communication made to the concerned agencies and staff. 2 day The staff to be trained will become aware of exactly when and where they need to report for training.

6 Sites for training management and technical staff will be set up. 1 day Sites to be used in each of the two initial training sessions will be set up, with arrangements for the preparation of other sites to be used in future also being made.

7 A review of the curriculum, materials and programs to be used in training of management and technical staff will be done. 1 day The materials, programs and curricula to be used in training will be revised and ready.

8 Training of management staff will take place in rounds, with a total of 8 sessions being carried out simultaneously in 2 different locations occurring (A total of 16 groups trained). 16 days Technicians and upper management will be prepared to implement and use the new Link Up system, as well as train other employees.

9 Upper management and technicians, who will have participated in training, will prepare and submit schedules for training of employees from the individual centers, agencies and counties (all 83). 1 day Schedules and timetables for the training of employees from the 83 counties and partner agencies will be ready.

10 A review of schedules materials and curricula to be used in the training of employees from the different counties will be done and approved .5 day Counties and agencies will be ready to carry out training sessions.

11 Initial training of employees will take place simultaneously in different counties and agencies over an extended period. 30 days Employees will become aware of what the program entails as well as how to use the new system that will be in place.

12 Site administrators and trainers from individual counties and agencies, will meet management in order to add any new employees that may have come in between training sessions 5 days New employees will continuously be added into the training schedule and be incorporated into the employee roster so as to ensure 100% training for employees.

13 Management to update employees at weekly team meetings and include practice sessions to further enhance an understanding and the adoption of the new program. 20 days Employees will become aware of any changes in training schedules or program

14 All employees will be entered into the Link Up system and necessary permissions and securities set 2 days The employees to use the system as well as their levels of permissions will be set and the employees made aware.

15 A beta test run shall be instituted involving up to 10 counties and agencies, with some employees being used as model patients. 1 day Glitches and potential problem areas shall be identified.

16 Revision and correction of glitches and problem areas, as well as the establishment of a team of technicians to help in solving any future problems shall be done. 3 days Adjustments to the Link Up system will occur and a technical support team selected.

17 Submission of a completion report to Community Mental Health Services Regional office shall be done. 1 day The project will be ready for implementation.

18 The Link up program will be implemented 1 day The Mental Health system in the state of Michigan will change to Link Up and direct communication between all the service providers done.

19 Continuous appraisal and improvement of the system will be done. Open The system will be upgraded continuously.

2433320267335Identification of agency, county and knowledge needs (0.5 days)

Identification of agency, county and knowledge needs (0.5 days)

PERT Chart

-5086352380615Meeting with site managers for scheduling of technicians and upper management training (0.5 days)

Meeting with site managers for scheduling of technicians and upper management training (0.5 days)

51758855986780Submissions to the Community Mental Health Services Regional office (1 day)

Submissions to the Community Mental Health Services Regional office (1 day)

27787607526655Beta Test run (1 day)

Beta Test run (1 day)

-2933707582535Enrollment of all employees into the Link Up system (2 days)

Enrollment of all employees into the Link Up system (2 days)

-5086356485890Addition of new employees to the roster and training schedule (5 days)

Addition of new employees to the roster and training schedule (5 days)

26549356835140Weekly updates for employees(20

Weekly updates for employees(20

-5086355497830Training of technical staff and upper management (16 days)

Training of technical staff and upper management (16 days)

-4483104697095Review of training material and program (1 day)

Review of training material and program (1 day)

-5086353234690Posting of training schedules (2 days

Posting of training schedules (2 days

-4483103981450Setting up of training sites (1 day)

Setting up of training sites (1 day)

45764457009130Implementation of the Link Up project (1 day)

Implementation of the Link Up project (1 day)

48393354590415Correction of any potential glitches, and the establishment of a support team. (3 days)

Correction of any potential glitches, and the establishment of a support team. (3 days)

25590505986780Initial training of employees (30 days)

Initial training of employees (30 days)

25590505085715Review and revision of the submitted material (0.5 days)

Review and revision of the submitted material (0.5 days)

25590503653790Preparation, and submission of training schedules for employees by the trained staff. (1day)

Preparation, and submission of training schedules for employees by the trained staff. (1day)

35883851595755Procurement of software and hardware required (10 days)

Procurement of software and hardware required (10 days)

-2933701595755Training of site administrators and management (5 days)

Training of site administrators and management (5 days)

Gantt Chart

ID Task Name Start Finish Duration Feb. March April May June July Aug. September October

1 Agency Iden 25 Feb 25 Feb 0.5d 2 Training 26 Feb 2 Mar 5days 3 Procuremen 26 Feb 7 Mar 10 days 4 Meeting 8 Mar 8 Mar 0.5 days 5 Schedule P. 9 Mar 10 Ma 2 days 6 Training Site 11 Mar 11Mar 1 day 7 Review 12 Mar 12 Ma 1 day 8 Training 13 Mar 29 Ma 16 days 9 Schedule 30 Mar 30 Ma 1 day 10 Review 1 April 1 April 0.5 d 11 Initial Traini. 2 April 1 May 30 days 12 New Employ 2 May 7 May 5 days 13 Updates 7 May 23 Oct 20 days 14 Registration 8 Mar. 9 Mar. 2 days 15 Test Run 13 Oct 13 Oct 1 day 16 Corrections 14 Oct 16 Oct 3 days 17 Regional Off 23 Oct 23 Oct 1 day 18 Implement. 31 Oct 31 Oct 1 day Scheduling constraints

The project will be designed to achieve a common goal within a specified time. However, the implementation stage is designed in stages whereby every stage is expected to achieve a certain goal within a specified time. In projecting and allocating the time expected for each stage certain constraints will be observed. The following are five main constraints:

All technicians and upper management staff cannot be obtained at the same time from all 83 counties as it would cripple mental health services in the state of Michigan.

Health care system is a critical sector and limiting the number of staff, technicians and upper management available for duty in the industry in the entire Michigan state can have serious negative consequences. For these reason, the new project implementation should be designed in a way that ensures the stability of healthcare system is not negatively affected. During training, each county is expected to provide two health care stakeholders; a technician and a member upper management and during for all counties may result to shortage in the mental health clinics especially for small health clinics for some counties.

There are only two training teams for training technicians and management staff.

The project development stage is designed to provide training to counties is different groups and in different days. Meaning that since there will be two training groups the counties will be grouped into two groups for the training to be effective. Each training team will group the counties assigned in groups of five counties and each group will be trained for one, meaning that each training a team a group of five counties and a total of ten counties will be trained in a day. Therefore, the scheduling the entire project duration consideration will be taken on the training period.

There are a number of hardware upgrades that might need to be done in some counties before training can be done , the time required for procuring these reduces the time available for training.

There are two stages of training to be completed before final implementation of the project. The project is designed to provide training to all the members who will be involved in its implementation. To begin with, training will be provided to a few technicians and upper management members who will act as pioneers in their respective counties. After their training has been completed, they will be expected to design a curriculum as well as a schedule on how they will train the other healthcare practitioners in the counties. The two stages of training for all the members will take time but will be essential in ensuring proper implementation of the project.

The time allocated for correcting glitches identified after the beta test run will depend on how early employee training is completed. This means that training stage will be essential for the project but this will later be followed by a testing or feedback stage. This stage be used to develop a beta test run which will be essential for determining whether the project is actually positive for the health care industry in the state of Michigan.

Specific Risks that will be encountered with using the front-loaded schedule

The project will really on a frontloaded schedule for its design and planning. Front-loaded schedule means that the project will be developed using conceptual development process which with the main focus being on planning using strategic information. Front loaded schedule which is also referred to as pre-project planning schedule has several advantages when addressing risk. This is because it focuses on ways of minimizing risk by analyzing all available resources. However, the schedule will encounter several risks such as inability to tackle unexpected risks that mostly arise for external resources. This scheduling system does not also provide accurate financial statements since it relies heavy on estimates rather than actual figures. Bottom line, the project is expected to be successful under the front loaded scheduling system since the risks associated with the system are minimal compared to its expected strengths.

Limits Of Urban Renewal In Greater St. Louis

Limits Of Urban Renewal In Greater St. Louis

Introduction

The redevelopment and urban renewal programs avoided neighborhoods that were declining immensely and were unsuccessful in curbing the decline of Central St. Louis. This failure may have resulted from a combination of bad policy, shallow resources and immense challenges. Initially, the city council was concerned about the substandard living conditions, an aspect that changed after the war with economic development becoming more of a priority than residential renewal, and focus being placed on the central business district rather than the troubled neighborhoods. However, St. Louis was not alone in this failure as urban renewal efforts in other American cities had similar results. The indefinable nature of the solution was a reflection of the elusive nature of the problem and a common set of conditions including fragmented governance, deindustrialization and limited resources. Of particular note is the fact that the term “blight” did not have a universal definition. Indeed, the local efforts for addressing urban conditions was heavily dependent on threats to moral order, safety and health that animated the powers of local police, considering that the only significant legal footing for urban reform was built on police power. After the war, the definition and determination of blighted areas was left to state governments thereby allowing local governments and redevelopment corporations to determine what blight meant. In legal terms, the most immense challenge revolved around the reconciliation of the definition of the term with the predisposing assumption that redevelopment served public interest, and the eminent domain powers that it enabled. The controversy increased in instances where these programs benefited certain individuals. However, the courts stated that the fact that these programs benefited some individuals more than others did not deprive them of their public character.

While the ambiguity in definition of “blight” was an impediment, redevelopment interests and local municipals appreciated its ambiguity as the definition was at their discretion. The problem with the local discretion revolved around the fact that the designation usually took place on proposal-by-proposal basis, in which case investment would be diverted from the most dismal urban conditions since private interests were looking for the “appropriate kind of blight”. As much as finding blight was considerably the discretion of local officials, they required a credible case that a redevelopment area deserved public attention or subsidy. The feat was accomplished through expanding the redevelopment area as it was easier to find blighted areas and use the excuse of “public interest” so as to counter the affected property owners’ objections. Of particular note, however, is the fact that the urban development policy was still distracted by the concerns of business leaders, realtors and developers that represented the CBD. Business interests often view redevelopment policies with skepticism or contempt due to the threats to public domain. Redevelopment efforts often started with the warehousing of dislocate residents of high-density public housing, which often ran into problems as the city inflated its capacity to assist individuals that were losing their homes. This resulted in the association of urban renewal programs with Negro removal.

It is imperative that further research is done to explore the reasons as to why the redevelopment and rebuilding efforts were slower propositions even when it was considerably easy to obtain the federal money for clearance. In addition, what patterns did these redevelopment and rebuilding efforts or programs follow and what was the influence of race in the particular patterns exhibited by the redevelopment patterns.