Q. do they deploy A LOT!?...is the job fun???...do they have a dangerous job??? any info will be appreciated
A. You're looking at an old AFSC. We no longer have 3C0X1, they split us all up into the new 3D career field. My job prior to the merger was Computer Systems Operations so I can answer all of this for you.
We fit right in the middle when it comes to deployment. Currently, if we do deploy it'll be for 6 months. You can expect to deploy every 2-3 years with this field.
Do you enjoy working on computers? Taking them apart, fixing them, finding all the issues a computer might have, fixing every computer that has problems on base, installing and uninstalling software? There's a good chance you'll be help desk with this job, which means you'll answer calls whenever someone has an issue with their computer. The other half actually goes out and fixes those problems. One thing I've noticed with this job is you have to be ready to take a lot of flak, people always think the world is going to go crashing down if they don't have their computer to do their work.
Dangerous? It's computers, how dangerous could it be? The only time I've been shocked was with a trick pen someone had because others kept taking his pens. As long as you have common sense it isn't a dangerous job at all.
We fit right in the middle when it comes to deployment. Currently, if we do deploy it'll be for 6 months. You can expect to deploy every 2-3 years with this field.
Do you enjoy working on computers? Taking them apart, fixing them, finding all the issues a computer might have, fixing every computer that has problems on base, installing and uninstalling software? There's a good chance you'll be help desk with this job, which means you'll answer calls whenever someone has an issue with their computer. The other half actually goes out and fixes those problems. One thing I've noticed with this job is you have to be ready to take a lot of flak, people always think the world is going to go crashing down if they don't have their computer to do their work.
Dangerous? It's computers, how dangerous could it be? The only time I've been shocked was with a trick pen someone had because others kept taking his pens. As long as you have common sense it isn't a dangerous job at all.
what is so important about testing stage of System development life cycle?
Q.
A. DEFINITION: System Development Life Cycle (SDLC) is the overall process of developing information systems through a multistep process from investigation of initial requirements through analysis, design, implementation and maintenance. There are many different models and methodologies, but each generally consists of a series of defined steps or stages.
MAY 14, 2002 (COMPUTERWORLD) - Once upon a time, software development consisted of a programmer writing code to solve a problem or automate a procedure. Nowadays, systems are so big and complex that teams of architects, analysts, programmers, testers and users must work together to create the millions of lines of custom-written code that drive our enterprises.
To manage this, a number of system development life cycle (SDLC) models have been created: waterfall, fountain, spiral, build and fix, rapid prototyping, incremental, and synchronize and stabilize.
The oldest of these, and the best known, is the waterfall: a sequence of stages in which the output of each stage becomes the input for the next. These stages can be characterized and divided up in different ways, including the following:
Project planning, feasibility study: Establishes a high-level view of the intended project and determines its goals.
Systems analysis, requirements definition: Refines project goals into defined functions and operation of the intended application. Analyzes end-user information needs.
Systems design: Describes desired features and operations in detail, including screen layouts, business rules, process diagrams, pseudocode and other documentation.
Implementation: The real code is written here.
Integration and testing: Brings all the pieces together into a special testing environment, then checks for errors, bugs and interoperability.
Acceptance, installation, deployment: The final stage of initial development, where the software is put into production and runs actual business.
Maintenance: What happens during the rest of the software's life: changes, correction, additions, moves to a different computing platform and more. This, the least glamorous and perhaps most important step of all, goes on seemingly forever.
But It Doesn't Work!
The waterfall model is well understood, but it's not as useful as it once was. In a 1991 Information Center Quarterly article, Larry Runge says that SDLC "works very well when we are automating the activities of clerks and accountants. It doesn't work nearly as well, if at all, when building systems for knowledge workers -- people at help desks, experts trying to solve problems, or executives trying to lead their company into the Fortune 100."
Another problem is that the waterfall model assumes that the only role for users is in specifying requirements, and that all requirements can be specified in advance. Unfortunately, requirements grow and change throughout the process and beyond, calling for considerable feedback and iterative consultation. Thus many other SDLC models have been developed.
The fountain model recognizes that although some activities can't start before others -- such as you need a design before you can start coding -- there's a considerable overlap of activities throughout the development cycle.
The spiral model emphasizes the need to go back and reiterate earlier stages a number of times as the project progresses. It's actually a series of short waterfall cycles, each producing an early prototype representing a part of the entire project. This approach helps demonstrate a proof of concept early in the cycle, and it more accurately reflects the disorderly, even chaotic evolution of technology.
Build and fix is the crudest of the methods. Write some code, then keep modifying it until the customer is happy. Without planning, this is very open-ended and can by risky.
In the rapid prototyping (sometimes called rapid application development) model, initial emphasis is on creating a prototype that looks and acts like the desired product in order to test its usefulness. The prototype is an essential part of the requirements determination phase, and may be created using tools different from those used for the final product. Once the prototype is approved, it is discarded and the "real" software is written.
The incremental model divides the product into builds, where sections of the project are created and tested separately. This approach will likely find errors in user requirements quickly, since user feedback is solicited for each stage and because code is tested sooner after it's written.
Big Time, Real Time
The synchronize and stabilize method combines the advantages of the spiral model with technology for overseeing and managing source code. This method allows many teams to work efficiently in parallel. This approach was defined by David Yoffie of Harvard University and Michael Cusumano of MIT. They studied how Microsoft Corp. developed Internet Explorer and Netscape Communications Corp. developed Communicator, finding common threads in the ways the two companies worked. For example, both companies did a nightly compilation (called a build) of the entire project, bringing together all the current components. They established release dates and expended considerable effort to stabilize the code before it was released. The companies did an alpha release for internal testing; one or more beta releases (usually feature-complete) for wider testing outside the company, and finally a release candidate leading to a gold master, which was released to manufacturing. At some point before each release, specifications would be frozen and the remaining time spent on fixing bugs.
Both Microsoft and Netscape managed millions of lines of code as specifications changed and evolved over time. Design reviews and strategy sessions were frequent, and everything was documented. Both companies built contingency time into their schedules, and when release deadlines got close, both chose to scale back product features rather than let milestone dates slip.
MAY 14, 2002 (COMPUTERWORLD) - Once upon a time, software development consisted of a programmer writing code to solve a problem or automate a procedure. Nowadays, systems are so big and complex that teams of architects, analysts, programmers, testers and users must work together to create the millions of lines of custom-written code that drive our enterprises.
To manage this, a number of system development life cycle (SDLC) models have been created: waterfall, fountain, spiral, build and fix, rapid prototyping, incremental, and synchronize and stabilize.
The oldest of these, and the best known, is the waterfall: a sequence of stages in which the output of each stage becomes the input for the next. These stages can be characterized and divided up in different ways, including the following:
Project planning, feasibility study: Establishes a high-level view of the intended project and determines its goals.
Systems analysis, requirements definition: Refines project goals into defined functions and operation of the intended application. Analyzes end-user information needs.
Systems design: Describes desired features and operations in detail, including screen layouts, business rules, process diagrams, pseudocode and other documentation.
Implementation: The real code is written here.
Integration and testing: Brings all the pieces together into a special testing environment, then checks for errors, bugs and interoperability.
Acceptance, installation, deployment: The final stage of initial development, where the software is put into production and runs actual business.
Maintenance: What happens during the rest of the software's life: changes, correction, additions, moves to a different computing platform and more. This, the least glamorous and perhaps most important step of all, goes on seemingly forever.
But It Doesn't Work!
The waterfall model is well understood, but it's not as useful as it once was. In a 1991 Information Center Quarterly article, Larry Runge says that SDLC "works very well when we are automating the activities of clerks and accountants. It doesn't work nearly as well, if at all, when building systems for knowledge workers -- people at help desks, experts trying to solve problems, or executives trying to lead their company into the Fortune 100."
Another problem is that the waterfall model assumes that the only role for users is in specifying requirements, and that all requirements can be specified in advance. Unfortunately, requirements grow and change throughout the process and beyond, calling for considerable feedback and iterative consultation. Thus many other SDLC models have been developed.
The fountain model recognizes that although some activities can't start before others -- such as you need a design before you can start coding -- there's a considerable overlap of activities throughout the development cycle.
The spiral model emphasizes the need to go back and reiterate earlier stages a number of times as the project progresses. It's actually a series of short waterfall cycles, each producing an early prototype representing a part of the entire project. This approach helps demonstrate a proof of concept early in the cycle, and it more accurately reflects the disorderly, even chaotic evolution of technology.
Build and fix is the crudest of the methods. Write some code, then keep modifying it until the customer is happy. Without planning, this is very open-ended and can by risky.
In the rapid prototyping (sometimes called rapid application development) model, initial emphasis is on creating a prototype that looks and acts like the desired product in order to test its usefulness. The prototype is an essential part of the requirements determination phase, and may be created using tools different from those used for the final product. Once the prototype is approved, it is discarded and the "real" software is written.
The incremental model divides the product into builds, where sections of the project are created and tested separately. This approach will likely find errors in user requirements quickly, since user feedback is solicited for each stage and because code is tested sooner after it's written.
Big Time, Real Time
The synchronize and stabilize method combines the advantages of the spiral model with technology for overseeing and managing source code. This method allows many teams to work efficiently in parallel. This approach was defined by David Yoffie of Harvard University and Michael Cusumano of MIT. They studied how Microsoft Corp. developed Internet Explorer and Netscape Communications Corp. developed Communicator, finding common threads in the ways the two companies worked. For example, both companies did a nightly compilation (called a build) of the entire project, bringing together all the current components. They established release dates and expended considerable effort to stabilize the code before it was released. The companies did an alpha release for internal testing; one or more beta releases (usually feature-complete) for wider testing outside the company, and finally a release candidate leading to a gold master, which was released to manufacturing. At some point before each release, specifications would be frozen and the remaining time spent on fixing bugs.
Both Microsoft and Netscape managed millions of lines of code as specifications changed and evolved over time. Design reviews and strategy sessions were frequent, and everything was documented. Both companies built contingency time into their schedules, and when release deadlines got close, both chose to scale back product features rather than let milestone dates slip.
what is diffrence between winxp home edition & winxp professional?
Q.
A. Although the XP Pro and Home Editions share the same common core code, they don't have the same features. The right version for you depends on the functionality you need. Think of XP Pro as a superset of XP Home. Below is a short list of supported features:
BackupâXP Pro has the standard Win2K backup program; XP Home has no backup program.
Dynamic DisksâXP Pro supports dynamic disks; XP Home doesn't.
IISâXP Pro includes IIS; XP Home doesn't.
Encrypted File System (EFS)âEFS debuted in Win2K and lets you encrypt files on an NTFS partition, a very useful feature for mobile machines. XP Pro includes EFS; XP Home doesn't.
MultiprocessorâXP Pro supports up to two processors; XP Home supports only one (as did Windows Me/Win98).
Remote AssistanceâBoth editions support Remote Assistance, which lets someone from a Help desk connect to the client desktop to troubleshoot problems.
Remote DesktopâXP Pro adds to Remote Assistance by letting any machine running a Terminal Services client run one Terminal Services session against an XP Pro machine.
Domain MembershipâXP Pro systems can be domain members; XP Home systems can't, but they can access domain resources.
Group PolicyâXP Pro supports group policies; XP Home doesn't.
IntelliMirrorâXP Pro supports IntelliMirror, which includes Microsoft Remote Installation Services (RIS), software deployment, and user setting management; XP Home doesn't support IntelliMirror.
Upgrade from Windows Me/Win98âBoth XP Pro and XP Home support this upgrade.
Upgrade from Win2K/NTâOnly XP Pro supports this upgrade.
64-bit SupportâOnly XP Pro will have a 64-bit version that supports the Itanium systems.
Network SupportâXP Pro includes support for Network Monitor, SNMP, IP Security (IPSec), and the Client Services for NetWare (CSNW); XP Home doesn't.
BackupâXP Pro has the standard Win2K backup program; XP Home has no backup program.
Dynamic DisksâXP Pro supports dynamic disks; XP Home doesn't.
IISâXP Pro includes IIS; XP Home doesn't.
Encrypted File System (EFS)âEFS debuted in Win2K and lets you encrypt files on an NTFS partition, a very useful feature for mobile machines. XP Pro includes EFS; XP Home doesn't.
MultiprocessorâXP Pro supports up to two processors; XP Home supports only one (as did Windows Me/Win98).
Remote AssistanceâBoth editions support Remote Assistance, which lets someone from a Help desk connect to the client desktop to troubleshoot problems.
Remote DesktopâXP Pro adds to Remote Assistance by letting any machine running a Terminal Services client run one Terminal Services session against an XP Pro machine.
Domain MembershipâXP Pro systems can be domain members; XP Home systems can't, but they can access domain resources.
Group PolicyâXP Pro supports group policies; XP Home doesn't.
IntelliMirrorâXP Pro supports IntelliMirror, which includes Microsoft Remote Installation Services (RIS), software deployment, and user setting management; XP Home doesn't support IntelliMirror.
Upgrade from Windows Me/Win98âBoth XP Pro and XP Home support this upgrade.
Upgrade from Win2K/NTâOnly XP Pro supports this upgrade.
64-bit SupportâOnly XP Pro will have a 64-bit version that supports the Itanium systems.
Network SupportâXP Pro includes support for Network Monitor, SNMP, IP Security (IPSec), and the Client Services for NetWare (CSNW); XP Home doesn't.
Powered by Yahoo! Answers
No comments:
Post a Comment