Jump to content

Edit filter log

Details for log entry 9908021

17:23, 29 January 2014: 50.84.88.230 (talk) triggered filter 554, performing the action "edit" on Systems analyst. Actions taken: none; Filter description: top100 blog charts (examine | diff)

Changes made in edit



Perhaps the most difficult task in system analysis is identfying the specific requirements that the system must satisfy. These requirements often are called user requirements because users provide them. When the system developers have accumulated the user requirements for the new system, they proceed to the system design stage.
Perhaps the most difficult task in system analysis is identfying the specific requirements that the system must satisfy. These requirements often are called user requirements because users provide them. When the system developers have accumulated the user requirements for the new system, they proceed to the system design stage.

==In popular culture==


The American humor publication [[The Onion]] consistently features a systems analyst on its (fake) panel of "American Voices," a spoof of [[man-on-the-street]] journalism. The systems analyst's take on the issue at hand is typically given next to two other individuals with absurd professions (such as "spelunking instructor").
The American humor publication [[The Onion]] consistently features a systems analyst on its (fake) panel of "American Voices," a spoof of [[man-on-the-street]] journalism. The systems analyst's take on the issue at hand is typically given next to two other individuals with absurd professions (such as "spelunking instructor").

Action parameters

VariableValue
Edit count of the user (user_editcount)
null
Name of the user account (user_name)
'50.84.88.230'
Age of the user account (user_age)
0
Groups (including implicit) the user is in (user_groups)
[ 0 => '*' ]
Whether or not a user is editing through the mobile interface (user_mobile)
false
Page ID (page_id)
12098689
Page namespace (page_namespace)
0
Page title without namespace (page_title)
'Systems analyst'
Full page title (page_prefixedtitle)
'Systems analyst'
Last ten users to contribute to the page (page_recent_contributors)
[ 0 => 'Aurelius139', 1 => 'Kkm010', 2 => 'ClueBot NG', 3 => '195.194.168.59', 4 => 'Omnipaedista', 5 => 'SFK2', 6 => 'Siemka256', 7 => 'Versageek', 8 => '65.199.36.3', 9 => 'Bananaear1' ]
Action (action)
'edit'
Edit summary/reason (summary)
''
Whether or not the edit is marked as minor (no longer in use) (minor_edit)
false
Old page wikitext, before the edit (old_wikitext)
'{{merge|Computer systems analyst|discuss=Talk:Systems analyst|date=June 2013}} A '''systems analyst''' researches problems, plans solutions, recommends [[software]] and systems, at least at the functional level, and coordinates development to meet [[business]] or other requirements. Although they may be familiar with a variety of programming languages, operating systems, and [[computer hardware]] platforms, they do not normally involve themselves in the actual hardware or software development. Because they often write user requests into technical specifications, the systems analysts are the [[Liaison job|liaison]]s between [[vendor]]s and [[information technology]] professionals.<ref name="Shelly et al.">Shelly, Gary B., Cashman, Thomas J., & Vermaat, Misty E. ''Discovering Computers 2008, Complete.'' Boston: Thomson Course Technology. ISBN 10: 1 -4239-1205-5</ref> They may be responsible for developing cost analysis, design considerations, staff impact amelioration, and implementation time-lines. A systems analyst may: * Identify, understand and plan for organizational and human impacts of planned systems, and ensure that new technical requirements are properly integrated with existing processes and skill sets. * Plan a system flow from the ground up. * Interact with internal users and customers to learn and document requirements that are then used to produce business requirements documents. * Write technical requirements from a critical phase. * Interact with designers to understand software limitations. * Help programmers during system development, ex: provide [[use cases]], [[flowcharts]] or even [[database design]]. * Perform system testing. * Deploy the completed system. * Document requirements or contribute to user manuals. * Whenever a development process is conducted, the system analyst is responsible for designing components and providing that information to the developer. The system development life cycle (SDLC) is the traditional system development method that organizations use for large-scale IT Projects. The SDLC is a structured framework that consists of sequential processes by which information system are developed. # System Investigation # System Analysis # System Design # Programming and Testing # Implementation # Operation and Maintenance System analysts are IT Professionals who specialize in analyzing and designing information systems. Once a development project has the necessary approvals from all participants, the systems analysis stage begins. System analysis is the examination of the business problem that organizations plan to solve with an information system. The main purpose of the systems analysis stage is to gather information about the existing system in order to determine the requirements for an enhanced system or a new system. The end product of this stage, known as the deliverable, is a set of system requirements.<br /> Perhaps the most difficult task in system analysis is identfying the specific requirements that the system must satisfy. These requirements often are called user requirements because users provide them. When the system developers have accumulated the user requirements for the new system, they proceed to the system design stage. The American humor publication [[The Onion]] consistently features a systems analyst on its (fake) panel of "American Voices," a spoof of [[man-on-the-street]] journalism. The systems analyst's take on the issue at hand is typically given next to two other individuals with absurd professions (such as "spelunking instructor"). ==See also== *[[Change management analyst]] *[[Computer systems analyst]] *[[Business analyst]] *[[Software analyst]] *[[Business analysis]] == References == {{reflist}} ==External links== * The US Department of Labor's description of "[http://www.bls.gov/ooh/computer-and-information-technology/computer-systems-analysts.htm Computer Systems Analysts]" [[Category:Systems analysis]] [[Category:Business and financial operations occupations]] [[Category:Computer occupations]] [[de:Systemanalyse#Informatik]]'
New page wikitext, after the edit (new_wikitext)
'{{merge|Computer systems analyst|discuss=Talk:Systems analyst|date=June 2013}} A '''systems analyst''' researches problems, plans solutions, recommends [[software]] and systems, at least at the functional level, and coordinates development to meet [[business]] or other requirements. Although they may be familiar with a variety of programming languages, operating systems, and [[computer hardware]] platforms, they do not normally involve themselves in the actual hardware or software development. Because they often write user requests into technical specifications, the systems analysts are the [[Liaison job|liaison]]s between [[vendor]]s and [[information technology]] professionals.<ref name="Shelly et al.">Shelly, Gary B., Cashman, Thomas J., & Vermaat, Misty E. ''Discovering Computers 2008, Complete.'' Boston: Thomson Course Technology. ISBN 10: 1 -4239-1205-5</ref> They may be responsible for developing cost analysis, design considerations, staff impact amelioration, and implementation time-lines. A systems analyst may: * Identify, understand and plan for organizational and human impacts of planned systems, and ensure that new technical requirements are properly integrated with existing processes and skill sets. * Plan a system flow from the ground up. * Interact with internal users and customers to learn and document requirements that are then used to produce business requirements documents. * Write technical requirements from a critical phase. * Interact with designers to understand software limitations. * Help programmers during system development, ex: provide [[use cases]], [[flowcharts]] or even [[database design]]. * Perform system testing. * Deploy the completed system. * Document requirements or contribute to user manuals. * Whenever a development process is conducted, the system analyst is responsible for designing components and providing that information to the developer. The system development life cycle (SDLC) is the traditional system development method that organizations use for large-scale IT Projects. The SDLC is a structured framework that consists of sequential processes by which information system are developed. # System Investigation # System Analysis # System Design # Programming and Testing # Implementation # Operation and Maintenance System analysts are IT Professionals who specialize in analyzing and designing information systems. Once a development project has the necessary approvals from all participants, the systems analysis stage begins. System analysis is the examination of the business problem that organizations plan to solve with an information system. The main purpose of the systems analysis stage is to gather information about the existing system in order to determine the requirements for an enhanced system or a new system. The end product of this stage, known as the deliverable, is a set of system requirements.<br /> Perhaps the most difficult task in system analysis is identfying the specific requirements that the system must satisfy. These requirements often are called user requirements because users provide them. When the system developers have accumulated the user requirements for the new system, they proceed to the system design stage. ==In popular culture== The American humor publication [[The Onion]] consistently features a systems analyst on its (fake) panel of "American Voices," a spoof of [[man-on-the-street]] journalism. The systems analyst's take on the issue at hand is typically given next to two other individuals with absurd professions (such as "spelunking instructor"). ==See also== *[[Change management analyst]] *[[Computer systems analyst]] *[[Business analyst]] *[[Software analyst]] *[[Business analysis]] == References == {{reflist}} ==External links== * The US Department of Labor's description of "[http://www.bls.gov/ooh/computer-and-information-technology/computer-systems-analysts.htm Computer Systems Analysts]" [[Category:Systems analysis]] [[Category:Business and financial operations occupations]] [[Category:Computer occupations]] [[de:Systemanalyse#Informatik]]'
Unified diff of changes made by edit (edit_diff)
'@@ -29,6 +29,8 @@ Perhaps the most difficult task in system analysis is identfying the specific requirements that the system must satisfy. These requirements often are called user requirements because users provide them. When the system developers have accumulated the user requirements for the new system, they proceed to the system design stage. +==In popular culture== + The American humor publication [[The Onion]] consistently features a systems analyst on its (fake) panel of "American Voices," a spoof of [[man-on-the-street]] journalism. The systems analyst's take on the issue at hand is typically given next to two other individuals with absurd professions (such as "spelunking instructor"). ==See also== '
New page size (new_size)
4120
Old page size (old_size)
4096
Size change in edit (edit_delta)
24
Lines added in edit (added_lines)
[ 0 => '==In popular culture==', 1 => false ]
Lines removed in edit (removed_lines)
[]
Whether or not the change was made through a Tor exit node (tor_exit_node)
0
Unix timestamp of change (timestamp)
1391016231