text:
Use case
From Wikipedia, the free encyclopedia
Jump to navigation Jump to search
A very simple use case diagram of a Wiki system.
Software development
Core activities
Processes
Requirements
Design
Engineering
Construction
Testing
Debugging
Deployment
Maintenance
Paradigms and models
Agile
Cleanroom
Incremental
Prototyping
Spiral
V model
Waterfall
Methodologies and frameworks
ASD
DevOps
DAD
DSDM
FDD
IID
Kanban
Lean SD
LeSS
MDD
MSF
PSP
RAD
RUP
SAFe
Scrum
SEMAT
TSP
UP
XP
Supporting disciplines
Configuration management
Documentation
Software quality assurance (SQA)
Project management
User experience
Practices
ATDD
BDD
CCO
CI
CD
DDD
PP
Stand-up
TDD
Tools
Compiler
Debugger
Profiler
GUI designer
Modeling
IDE
Build automation
Release automation
Infrastructure as Code
Testing
Standards and Bodies of Knowledge
BABOK
CMMI
IEEE standards
ISO 9001
ISO/IEC standards
PMBOK
SWEBOK
ITIL
Glossaries
Artificial intelligence
Computer science
Electrical and electronics engineering
v
t
e
In software and systems engineering, a use case is a list of actions or event steps typically defining the interactions between a role (known in the Unified Modeling Language as an actor) and a system to achieve a goal. The actor can be a human or other external system. In systems engineering use cases are used at a higher level than within software engineering often representing missions or stakeholder goals. The detailed requirements may then be captured in the Systems Modeling Language (SysML) or as contractual statements.
Use case analysis is an important and valuable requirement analysis technique that has been widely used in modern software engineering since its formal introduction by Ivar Jacobson in 1992. Use case driven development is a key characteristic of many process models and frameworks such as ICONIX, the Unified Process (UP), the IBM Rational Unified Process (RUP), and the Oracle Unified Method (OUM). With its inherent iterative, incremental and evolutionary nature, use case also fits well for agile development.
Contents
1 History
2 Templates
2.1 Cockburn style
2.1.1 Design scopes
2.1.2 Goal levels
2.1.3 Fully dressed
2.1.4 Casual
2.2 Fowler style
3 Actors
4 Business use case
5 Visual modeling
6 Examples
7 Advantages
8 Limitations
9 Misconceptions
10 Tools
11 See also
12 References
13 Further reading
14 External links
History[edit]
In 1986, Ivar Jacobson first formulated textual, structural, and visual modeling techniques for specifying use cases. In 1992 his co-authored book Object-Oriented Software Engineering - A Use Case Driven Approach[1] helped to popularize the technique for capturing functional requirements, especially in software development. Originally he had used the terms usage scenarios and usage case — the latter a direct translation of his Swedish term användningsfall — but found that neither of these terms sounded natural in English, and eventually he settled on use case.[2]
Since then, other experts have also contributed a great deal to the technique, notably Alistair Cockburn, Larry Constantine, Dean Leffingwell, Kurt Bittner and Gunnar Overgaard.
In 2011, Jacobson published an update to his work, called Use Case 2.0,[3] with the intention of incorporating many of his practical experiences of applying use cases since the original inception of the concept.[4][need quotation to verify]
Templates[edit]
There are many ways to write a use case in text, from use case brief, casual, outline, to fully dressed etc., and with varied templates. Writing use cases in templates devised by various vendors or experts is a common industry practice to get high-quality functional system requirements.
Cockburn style[edit]
The template defined by Alistair Cockburn in his popular book Writing Effective Use Cases has been one of the most widely used writing styles of use cases.[citation needed]
Design scopes[edit]
Cockburn suggests annotating each use case with a symbol to show the "Design Scope", which may be black-box (internal detail is hidden) or white-box (internal detail is shown). Five symbols are available:[5]
Scope
Icon
Organization (black-box) Filled House
Organization (white-box) Unfilled House
System (black-box) Filled Box
System (white-box) Unfilled Box
Component Screw or Bolt
Other authors sometimes call use cases at Organization level "Business use cases".[6]
Goal levels[edit]
Hierarchy of goal levels
Cockburn suggests annotating each use case with a symbol to show the "Goal Level";[7] the preferred level is "User-goal" (or colloquially "sea level"[8]:101).
Goal Level
Icon
Symbol
Very High Summary Cloud ++
Summary Flying Kite +
User Goal Waves at Sea !
Subfunction Fish -
Too Low Seabed Clam-Shell --
Sometimes in text writing, a use-case name followed by an alternative text symbol (!, +, -, etc.) is a more concise and convenient way to denote levels, e.g. place an order!, login-.
Fully dressed[edit]
Cockburn describes a more detailed structure for a use case, but permits it to be simplified when less detail is needed. His fully dressed use case template lists the following fields:[9]
Title: "an active-verb goal phrase that names the goal of the primary actor"[10]
Primary Actor
Goal in Context
Scope
Level
Stakeholders and Interests
Precondition
Minimal Guarantees
Success Guarantees
Trigger
Main Success Scenario
Extensions
Technology & Data Variations List
In addition, Cockburn suggests using two devices to indicate the nature of each use case: icons for design scope and goal level.
Cockburn's approach has influenced other authors; for example, Alexander and Beus-Dukic generalize Cockburn's "Fully dressed use case" template from software to systems of all kinds, with the following fields differing from Cockburn:[11]
Variation scenarios "(maybe branching off from and maybe returning to the main scenario)"
Exceptions "i.e. exception events and their exception-handling scenarios"
Casual[edit]
Cockburn recognizes that projects may not always need detailed "fully dressed" use cases. He describes a Casual use case with the fields:[9]
Title (goal)
Primary Actor
Scope
Level
(Story): the body of the use case is simply a paragraph or two of text, informally describing what happens.
Fowler style[edit]
Martin Fowler states "There is no standard way to write the content of a use case, and different formats work well in different cases."[8]:100 He describes "a common style to use" as follows:[8]:101
Title: "goal the use case is trying to satisfy"[8]:101
Main Success Scenario: numbered list of steps[8]:101
Step: "a simple statement of the interaction between the actor and a system"[8]:101
Extensions: separately numbered lists, one per Extension[8]:101
Extension: "a condition that results in different interactions from .. the main success scenario". An extension from main step 3 is numbered 3a, etc.[8]:101
The Fowler style can also be viewed as a simplified variant of the Cockburn template.
Actors[edit]
Main article: Actor (UML)
A use case defines the interactions between external actors and the system under consideration to accomplish a goal. Actors must be able to make decisions, but need not be human: "An actor might be a person, a company or organization, a computer program, or a computer system—hardware, software, or both."[12] Actors are always stakeholders, but not all stakeholders are actors, since they "never interact directly with the system, even though they have the right to care how the system behaves."[12] For example, "the owners of the system, the company's board of directors, and regulatory bodies such as the Internal Revenue Service and the Department of Insurance" could all be stakeholders but are unlikely to be actors.[12]
Similarly, a person using a system may be represented as different actors because of playing different roles. For example, user "Joe" could be playing the role of a Customer when using an Automated Teller Machine to withdraw cash from his own account, or playing the role of a Bank Teller when using the system to restock the cash drawer on behalf of the bank.
Actors are often working on behalf of someone else. Cockburn writes that "These days I write 'sales rep for the customer' or 'clerk for the marketing department' to capture that the user of the system is acting for someone else." This tells the project that the "user interface and security clearances" should be designed for the sales rep and clerk, but that the customer and marketing department are the roles concerned about the results.[13]
A stakeholder may play both an active and an inactive role: for example, a Consumer is both a "mass-market purchaser" (not interacting with the system) and a User (an actor, actively interacting with the purchased product).[14] In turn, a User is both a "normal operator" (an actor using the system for its intended purpose) and a "functional beneficiary" (a stakeholder who benefits from the use of the system).[14] For example, when user "Joe" withdraws cash from his account, he is operating the Automated Teller Machine and obtaining a result on his own behalf.
Cockburn advises to look for actors among the stakeholders of a system, the primary and supporting (secondary) actors of a use case, the system under design (SuD) itself, and finally among the "internal actors", namely the components of the system under design.[12]
Business use case[edit]
This section needs expansion. You can help by adding to it. (July 2015)
A business Use case diagram depicts a model of several business use cases (goals) which represents the interactions between a restaurant (the business system) and its primary stakeholders (business actors and business workers).
Visual modeling[edit]
UML diagram types
Structural UML diagrams
Class diagram
Component diagram
Composite structure diagram
Deployment diagram
Object diagram
Package diagram
Profile diagram
Behavioral UML diagrams
Activity diagram
Communication diagram
Interaction overview diagram
Sequence diagram
State diagram
Timing diagram
Use case diagram
v
t
e
Use cases are not only texts, but also diagrams, if needed. In the Unified Modeling Language, the relationships between use cases and actors are represented in use case diagrams originally based upon Ivar Jacobson's Objectory notation. SysML uses the same notation at a system block level.
In addition, other behavioral UML diagrams such as activity diagrams, sequence diagrams, communication diagrams and state machine diagrams can also be used to visualize use cases accordingly. Specifically, a System Sequence Diagram (SSD) is a sequence diagram often used to show the interactions between the external actors and the system under design (SuD), usually for visualizing a particular scenario of a use case.
Use case analysis usually starts by drawing use case diagrams. For agile development, a requirement model of many UML diagrams depicting use cases plus some textual descriptions, notes or use case briefs would be very lightweight and just enough for small or easy project use. As good complements to use case texts, the visual diagram representations of use cases are also effective facilitating tools for the better understanding, communication and design of complex system behavioral requirements.
Examples[edit]
Below is a sample use case written with a slightly-modified version of the Cockburn-style template. Note that there are no buttons, controls, forms, or any other UI elements and operations in the basic use case description, where only user goals, subgoals or intentions are expressed in every step of the basic flow or extensions. This practice makes the requirement specification clearer, and maximizes the flexibility of the design and implementations.
Use Case: Edit an article
Primary Actor: Member (Registered User)
Scope: a Wiki system
Level: ! (User goal or sea level)
Brief: (equivalent to a user story or an epic)
The member edits any part (the entire article or just a section) of an article he/she is reading. Preview and changes comparison are allowed during the editing.
Stakeholders
...
Postconditions
Minimal Guarantees:
Success Guarantees:
The article is saved and an updated view is shown.
An edit record for the article is created by the system, so watchers of the article can be informed of the update later.
Preconditions:
The article with editing enabled is presented to the member.
Triggers:
The member invokes an edit request (for the full article or just one section) on the article.
Basic flow:
The system provides a new editor area/box filled with all the article's relevant content with an informative edit summary for the member to edit. If the member just wants to edit a section of the article, only the original content of the section is shown, with the section title automatically filled out in the edit summary.
The member modifies the article's content till satisfied.
The member fills out the edit summary, tells the system if he/she wants to watch this article, and submits the edit.
The system saves the article, logs the edit event and finishes any necessary post processing.
The system presents the updated view of the article to the member.
Extensions:
2-3.
a. Show preview:
The member selects Show preview which submits the modified content.
The system reruns step 1 with addition of the rendered updated content for preview, and informs the member that his/her edits have not been saved yet, then continues.
b. Show changes:
The member selects Show changes which submits the modified content.
The system reruns step 1 with addition of showing the results of comparing the differences between the current edits by the member and the most recent saved version of the article, then continues.
c. Cancel the edit:
The member selects Cancel.
The system discards any change the member has made, then goes to step 5.
4a. Timeout:
...
Advantages[edit]
Since the inception of the agile movement, the user story technique from Extreme Programming has been so popular that many think it is the only and best solution for agile requirements of all projects. Alistair Cockburn lists five reasons why he still writes use cases in agile development.[15]
The list of goal names provides the shortest summary of what the system will offer (even than user stories). It also provides a project planning skeleton, to be used to build initial priorities, estimates, team allocation and timing.
The main success scenario of each use case provides everyone involved with an agreement as to what the system will basically do and what it will not do. It provides the context for each specific line item requirement (e.g. fine-grained user stories), a context that is very hard to get anywhere else.
The extension conditions of each use case provide a framework for investigating all the little, niggling things that somehow take up 80% of the development time and budget. It provides a look ahead mechanism, so the stakeholders can spot issues that are likely to take a long time to get answers for. These issues can and should then be put ahead of the schedule, so that the answers can be ready when the development team gets around to working on them.
The use case extension scenario fragments provide answers to the many detailed, often tricky and ignored business questions: “What are we supposed to do in this case?” It is a thinking/documentation framework that matches the if…then…else statement that helps the programmers think through issues. Except it is done at investigation time, not programming time.
The full use case set shows that the investigators have thought through every user’s needs, every goal they have with respect to the system, and every business variant involved.
In summary, specifying system requirements in use cases has these apparent benefits comparing with traditional or other approaches:
User focused
Use cases constitute a powerful, user-centric tool for the software requirements specification process.[16] Use case modeling typically starts from identifying key stakeholder roles (actors) interacting with the system, and their goals or objectives the system must fulfill (an outside perspective). These user goals then become the ideal candidates for the names or titles of the use cases which represent the desired functional features or services provided by the system. This user-centered approach ensure that what has the real business value and the user really want is developed, not those trivial functions speculated from a developer or system (inside) perspective.
Use case authoring has been an important and valuable analysis tool in the domain of User-Centered Design (UCD) for years.
Better communication
Use cases are often written in natural languages with structured templates. This narrative textual form (legible requirement stories), understandable by almost everyone, complemented by visual UML diagrams foster better and deeper communications among all stakeholders, including customers, end-users, developers, testers and managers. Better communications result in quality requirements and thus quality systems delivered.
Quality requirements by structured exploration
One of the most powerful things about use cases resides in the formats of the use case templates, especially the main success scenario (basic flow) and the extension scenario fragments (extensions, exceptional and/or alternative flows). Analyzing a use case step by step from preconditions to postconditions, exploring and investigating every action step of the use case flows, from basic to extensions, to identify those tricky, normally hidden and ignored, seemingly trivial but realistically often costly requirements (as Cockburn mentioned above), is a structured and beneficial way to get clear, stable and quality requirements systematically.
Minimizing and optimizing the action steps of a use case to achieve the user goal also contribute to a better interaction design and user experience of the system.
Facilitate testing and user documentation
With content based upon an action or event flow structure, a model of well-written use cases also serves as an excellent groundwork and valuable guidelines for the design of test cases and user manuals of the system or product, which is an effort-worthy investment up-front. There is obvious connections between the flow paths of a use case and its test cases. Deriving functional test cases from a use case through its scenarios (running instances of a use case) is straightforward.[17]
Limitations[edit]
Limitations of use cases include:
Use cases are not well suited to capturing non-interaction based requirements of a system (such as algorithm or mathematical requirements) or non-functional requirements (such as platform, performance, timing, or safety-critical aspects). These are better specified declaratively elsewhere.
As there are no fully standard definitions of use cases, each project must form its own interpretation.
Some use case relationships, such as extends, are ambiguous in interpretation and can be difficult for stakeholders to understand as pointed out by Cockburn (Problem #6)[18][citation needed]
Use case developers often find it difficult to determine the level of user interface (UI) dependency to incorporate in a use case. While use case theory suggests that UI not be reflected in use cases, it can be awkward to abstract out this aspect of design, as it makes the use cases difficult to visualize. In software engineering, this difficulty is resolved by applying requirements traceability, for example with a traceability matrix. Another approach to associate UI elements with use cases, is to attach a UI design to each step in the use case. This is called a use case storyboard.
Use cases can be over-emphasized. Bertrand Meyer discusses issues such as driving system design too literally from use cases, and using use cases to the exclusion of other potentially valuable requirements analysis techniques.[19]
Use cases are a starting point for test design,[20] but since each test needs its own success criteria, use cases may need to be modified to provide separate post-conditions for each path.[21]
Though use cases include goals and contexts, whether these goals and motivations behind the goals (stakeholders concerns and their assessments including non-interaction) conflict or negatively/positively affect other system goals are subject of goal oriented requirement modelling techniques (such as BMM, I*, KAOS and ArchiMate ARMOR).
Misconceptions[edit]
This section needs expansion. You can help by adding to it. (July 2015)
Common misunderstandings about use cases are:
User stories are agile; use cases are not.
Agile and Scrum are neutral on requirement techniques. As the Scrum Primer[22] states,
Product Backlog items are articulated in any way that is clear and sustainable. Contrary to popular misunderstanding, the Product Backlog does not contain "user stories"; it simply contains items. Those items can be expressed as user stories, use cases, or any other requirements approach that the group finds useful. But whatever the approach, most items should focus on delivering value to customers.
Use cases are mainly diagrams.
Craig Larman stresses that "use cases are not diagrams, they are text".[23]
Use cases have too much UI-related content.
As some put it,
Use cases will often contain a level of detail (i.e. naming of labels and buttons) which make it not well suited for capturing the requirements for a new system from scratch.
Novice misunderstandings. Each step of a well-written use case should present actor goals or intentions (the essence of functional requirements), and normally it should not contain any user interface details, e.g. naming of labels and buttons, UI operations etc., which is a bad practice and will unnecessarily complicate the use case writing and limit its implementation.
As for capturing requirements for a new system from scratch, use case diagrams plus use case briefs are often used as handy and valuable tools, at least as lightweight as user stories.
Writing use cases for large systems is tedious and a waste of time.
As some put it,
The format of the use case makes it difficult to describe a large system (e.g. CRM system) in less than several hundred pages. It is time consuming and you will find yourself spending time doing an unnecessary amount of rework.
Spending much time in writing tedious use cases which add no or little value and result in a lot of rework is a bad smell indicating that the writers are not well skilled and have little knowledge of how to write quality use cases both efficiently and effectively. Use cases should be authored in an iterative, incremental and evolutionary (agile) way. Applying use case templates does not mean that all the fields of a use case template should be used and filled out comprehensively from up-front or during a special dedicated stage, i.e. the requirement phase in the traditional waterfall development model.
In fact, the use case formats formulated by those popular template styles, e.g. the RUP's and the Cockburn's (also adopted by the OUM method) etc., have been proved in practice as valuable and helpful tools for capturing, analyzing and documenting complex requirements of large systems. The quality of a good use case documentation (model) should not be judged largely or only by its size. It is possible as well that a quality and comprehensive use case model of a large system may finally evolve into hundreds of pages mainly because of the inherent complexity of the problem in hand, not because of the poor writing skills of its authors.
Tools[edit]
This section does not cite any sources. Please help improve this section by adding citations to reliable sources. Unsourced material may be challenged and removed. (August 2013) (Learn how and when to remove this template message)
Text editors and/or word processors with template support are often used to write use cases. For large and complex system requirements, dedicated use case tools are helpful.
Some of the well-known use case tools include:
CaseComplete
Enterprise Architect
MagicDraw
Rational Software's RequisitePro - one of the early, well-known use case and requirement management tools in the 1990s.
Wiki software - good tools for teams to author and manage use cases collaboratively.
Most UML tools support both the text writing and visual modeling of use cases.
See also[edit]
Software Testing portal
Abuse case
Business case
Event partitioning
Feature
List of UML tools
Misuse case
Requirement
Requirements elicitation
Scenario
Storyboard
Test Case
Use Case Points
References[edit]
Jump up ^ Jacobson Ivar, Christerson Magnus, Jonsson Patrik, Övergaard Gunnar, Object-Oriented Software Engineering - A Use Case Driven Approach, Addison-Wesley, 1992.
Jump up ^ "Alistair Cockburn, "Use cases, ten years later"". Alistair.cockburn.us. 2002. Retrieved 2013-04-17.
Jump up ^ Jacobson, Ivar; Spence, Ian; Bittner, Kurt (December 2011). "Use Case 2.0: The Guide to Succeeding with Use Cases". Ivar Jacobson International. Retrieved 2014-05-05.
Jump up ^ "Business Analysis Conference Europe 2011 - 26-28 September 2011, London, UK". Irmuk.co.uk. Retrieved 2013-04-17.
Jump up ^ Cockburn, 2001. Inside front cover. Icons "Design Scope".
Jump up ^ Suzanne Robertson. Scenarios in Requirements Discovery. Chapter 3 in Alexander and Maiden, 2004. Pages 39-59.
Jump up ^ Cockburn, 2001. Inside front cover. Icons "Goal Level".
^ Jump up to: a b c d e f g h Fowler, 2004.
^ Jump up to: a b Cockburn, 2001. Page 120.
Jump up ^ Cockburn, 2001. Inside rear cover. Field "Use Case Title".
Jump up ^ Alexander and Beus-Dukic, 2009. Page 121
^ Jump up to: a b c d Cockburn, 2001. Page 53.
Jump up ^ Cockburn, 2001. Page 55.
^ Jump up to: a b Alexander and Beus-Dukic, 2009. Page 39.
Jump up ^ Cockburn, Alistair (2008-01-09). "Why I still use use cases". alistair.cockburn.us.
Jump up ^ Karl Wiegers (March 1997). "Listening to the Customer's Voice". Process Impact. Software Development.
Jump up ^ Peter Zielczynski (May 2006). "Traceability from Use Cases to Test Cases". IBM developerWorks.
Jump up ^ "Alistair.Cockburn.us - Structuring use cases with goals". alistair.cockburn.us. Retrieved 16 March 2018.
Jump up ^ Meyer, 2000. (page needed)
Jump up ^ Armour and Miller, 2000. (page needed)
Jump up ^ Denney, 2005. (page needed)
Jump up ^ Pete Deemer; Gabrielle Benefield; Craig Larman; Bas Vodde (2012-12-17). "The Scrum Primer: A Lightweight Guide to the Theory and Practice of Scrum (Version 2.0)". InfoQ.
Jump up ^ Larman, Craig. Applying UML and patterns. Prentice Hall. pp. 63–64. ISBN 0-13-148906-2.
Further reading[edit]
Alexander, Ian, and Beus-Dukic, Ljerka. Discovering Requirements: How to Specify Products and Services. Wiley, 2009.
Alexander, Ian, and Maiden, Neil. Scenarios, Stories, Use Cases. Wiley 2004.
Armour, Frank, and Granville Miller. Advanced Use Case Modeling: Software Systems. Addison-Wesley, 2000.
Kurt Bittner, Ian Spence, Use Case Modeling, Addison-Wesley Professional, Aug 20, 2002.
Cockburn, Alistair. Writing Effective Use Cases. Addison-Wesley, 2001.
Larry Constantine, Lucy Lockwood, Software for Use: A Practical Guide to the Essential Models and Methods of Usage-Centered Design, Addison-Wesley, 1999.
Denney, Richard. Succeeding with Use Cases: Working Smart to Deliver Quality. Addison-Wesley, 2005.
Fowler, Martin. UML Distilled (Third Edition). Addison-Wesley, 2004.
Jacobson Ivar, Christerson M., Jonsson P., Övergaard G., Object-Oriented Software Engineering - A Use Case Driven Approach, Addison-Wesley, 1992.
Jacobson Ivar, Spence I., Bittner K. Use Case 2.0: The Guide to Succeeding with Use Cases, IJI SA, 2011.
Dean Leffingwell, Don Widrig, Managing Software Requirements: A Use Case Approach, Addison-Wesley Professional. Dec 7, 2012.
Kulak, Daryl, and Eamonn Guiney. Use cases: requirements in context. Addison-Wesley, 2012.
Meyer, Bertrand. Object Oriented Software Construction. (2nd edition). Prentice Hall, 2000.
Schneider, Geri and Winters, Jason P. Applying Use Cases 2nd Edition: A Practical Guide. Addison-Wesley, 2001.
Wazlawick, Raul S. Object-Oriented Analysis and Design for Information Systems: Modeling with UML, OCL, and IFML. Morgan Kaufmann, 2014.
External links[edit]
Alistair Cockburn's use case column
Use Cases (Usability.gov)
Basic Use Case Template by Alistair Cockburn
Application of use cases for stakeholder analysis "Project Icarus: Stakeholder Scenarios for an Interstellar Exploration Program", JBIS, 64, 224-233
"An Academic Survey on the Role of Use Cases in the UML"
Search use case in IBM developerWorks
show
v
t
e
Unified Modeling Language
Actors
Organizations
Object Management Group
UML Partners
Persons
Grady Booch
Ivar Jacobson
James Rumbaugh
Concepts
Object oriented
Object-oriented programming
Object-oriented analysis and design
Object-oriented modeling
Structure
Actor
Attribute
Artifact
Class
Component
Interface
Object
Package
Profile diagram
Behavior
Activity
Event
Message
Method
State
Use case
Relationships
Association
Composition
Dependency
Generalization (or Inheritance)
Extensibility
Profile
Stereotype
Other
Multiplicity
Diagrams
Structure
Class
Component
Composite structure
Deployment
Object
Package
Behaviour
Activity
State Machine
Use case
Interaction
Communications
Sequence
Interaction overview
Timing
Derived languages
Systems Modeling Language (SysML)
UML eXchange Format (UXF)
XML Metadata Interchange (XMI)
Executable UML (xUML)
Other topics
Glossary of UML terms
Rational Unified Process
List of Unified Modeling Language tools
Object Modeling in Color
show
v
t
e
Software engineering
Fields
Computer programming
Requirements engineering
Software deployment
Software design
Software maintenance
Software testing
Systems analysis
Formal methods
Concepts
Data modeling
Enterprise architecture
Functional specification
Modeling language
Orthogonality
Programming paradigm
Software
Software archaeology
Software architecture
Software configuration management
Software development methodology
Software development process
Software quality
Software quality assurance
Software verification and validation
Structured analysis
Orientations
Agile
Aspect-oriented
Object orientation
Ontology
Service orientation
SDLC
Models
Developmental
Agile
EUP
Executable UML
Incremental model
Iterative model
Prototype model
RAD
UP
Scrum
Spiral model
V-Model
Waterfall model
XP
Other
SPICE
CMMI
Data model
ER model
Function model
Information model
Metamodeling
Object model
Systems model
View model
Languages
IDEF
UML
USL
SysML
Software
engineers
Victor Basili
Kent Beck
Grady Booch
Fred Brooks
Barry Boehm
Peter Chen
Danese Cooper
Ward Cunningham
Tom DeMarco
Edsger W. Dijkstra
Delores M. Etter
Martin Fowler
Adele Goldstine
Margaret Hamilton
C. A. R. Hoare
Lois Haibt
Mary Jean Harrold
Grace Hopper
Watts Humphrey
Michael A. Jackson
Ivar Jacobson
Alan Kay
Nancy Leveson
Stephen J. Mellor
Bertrand Meyer
David Parnas
Trygve Reenskaug
Winston W. Royce
James Rumbaugh
Mary Shaw
Peri Tarr
Elaine Weyuker
Niklaus Wirth
Edward Yourdon
Related fields
Computer science
Computer engineering
Project management
Risk management
Systems engineering
Category
Commons
Retrieved from "https://en.wikipedia.org/w/index.php?title=Use_case&oldid=858369454"
Categories:
Software project management
Software requirements
Unified Modeling Language
Systems Modeling Language
1986 establishments in Sweden
1986 in computer science
Swedish inventions
Agile software development
Hidden categories:
Use dmy dates from April 2011
Wikipedia articles needing factual verification from May 2014
All articles with unsourced statements
Articles with unsourced statements from March 2016
Articles to be expanded from July 2015
All articles to be expanded
Articles using small message boxes
Articles with unsourced statements from October 2013
Articles needing additional references from August 2013
All articles needing additional references
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
Namespaces
Article
Talk
Variants
Views
Read
Edit
View history
More
Search
Navigation
Main page
Contents
Featured content
Current events
Random article
Donate to Wikipedia
Wikipedia store
Interaction
Help
About Wikipedia
Community portal
Recent changes
Contact page
Tools
What links here
Related changes
Upload file
Special pages
Permanent link
Page information
Wikidata item
Cite this page
Print/export
Create a book
Download as PDF
Printable version
Languages
Afrikaans
العربية
Català
Čeština
Dansk
Deutsch
Español
فارسی
Français
한국어
Italiano
עברית
Nederlands
日本語
Norsk
Polski
Português
Русский
Shqip
Slovenčina
Suomi
Svenska
Türkçe
Українська
Tiếng Việt
中文
17 more
Edit links
This page was last edited on 6 September 2018, at 17:44 (UTC).
Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.
Privacy policy
About Wikipedia
Disclaimers
Contact Wikipedia
Developers
Cookie statement
Mobile view
Enable previews

values: mw-page-base noprint

values: mw-head-base noprint

values: firstHeading firstHeading en

values: siteSub noprint

attrs: class href

values: mw-jump-link #mw-head

values: mw-jump-link #p-search

value: p

attrs: href class title

attrs: class style

value: li

values:
/wiki/Software_development_methodology
mw-redirect
Software development methodology

values:
/wiki/Model-driven_development
mw-redirect
Model-driven development

values:
/wiki/Application_release_automation
mw-redirect
Application release automation

values: A Guide to the Business Analysis Body of Knowledge

values: Information Technology Infrastructure Library

values: Glossary of electrical and electronics engineering

values: Template talk:Software development process

values: float:right;clear:right;width:22.0em;margin:0 0 1.0em 1.0em;background:#f9f9f9;border:1px solid #aaa;padding:0.2em;border-spacing:0.4em 0;text-align:center;line-height:1.4em;font-size:88%

values:
/wiki/Requirement_analysis
mw-redirect
Requirement analysis

values: checkbox button toctogglecheckbox toctogglecheckbox display:none

values:
/wiki/Functional_requirements
mw-redirect
Functional requirements

values: Quotation needed from source to verify. (May 2014)

values: This claim needs references to reliable sources. (March 2016)

values:
noprint Inline-Template Template-Fact
white-space:nowrap;

attrs: alt src width height data-file-width data-file-height

values: plainlinks metadata ambox mbox-small-left ambox-content

values:
plainlist
padding:0 0.1em 0.4em;text-align:left

values: Timing diagram (Unified Modeling Language)

values:
/wiki/Use_Case_Diagram
mw-redirect
Use Case Diagram

values:
/wiki/System_Sequence_Diagram
mw-redirect
System Sequence Diagram

values:
/wiki/Extreme_Programming
mw-redirect
Extreme Programming

values:
/wiki/Agile_development
mw-redirect
Agile development

values:
/wiki/Non-functional_requirements
mw-redirect
Non-functional requirements

values: This claim needs references to reliable sources. (October 2013)

values:
/wiki/Scrum_(development)
mw-redirect
Scrum (development)

values: Help:Introduction to referencing with Wiki Markup/1

values: plainlinks metadata ambox ambox-content ambox-Unreferenced

values:
/wiki/List_of_UML_tools
mw-redirect
List of UML tools

values:
/wiki/Portal:Software_Testing
mw-redirect
Portal:Software Testing

values: display:table-cell;padding:0.2em 0.2em 0.2em 0.3em;vertical-align:middle

values: margin:0.5em 0 0.5em 1em;border:solid #aaa 1px

values: Ian Spence (software engineer) (page does not exist)

values:
nofollow
http://www.irmuk.co.uk/BA2011/
external text

values: -moz-column-width: 40em; -webkit-column-width: 40em; column-width: 40em; list-style-type: decimal;

values:
nofollow
external text
http://alistair.cockburn.us/Use+cases

values:
nofollow
https://www.uleth.ca/survey/uml/
external text

values:
navbox-image
5
width:1px;padding:0px 0px 0px 2px

values: Glossary of Unified Modeling Language terms

values: nowraplinks collapsible autocollapse navbox-inner mw-collapsible mw-made-collapsible mw-collapsed

values: nowraplinks hlist collapsible autocollapse navbox-inner mw-collapsible mw-made-collapsible mw-collapsed

values: Category:Wikipedia articles needing factual verification from May 2014

values: Category:All articles with unsourced statements

values: Category:Articles with unsourced statements from March 2016

values: Category:Articles to be expanded from July 2015

values: Category:Articles using small message boxes

values: Category:Articles with unsourced statements from October 2013

values: Category:Articles needing additional references from August 2013

values: Category:All articles needing additional references

values: Discussion about edits from this IP address [ctrl-alt-n]

values: A list of edits made from this IP address [ctrl-alt-y]

values: You are encouraged to create an account and log in; however, it is not mandatory

values: You're encouraged to log in; however, it's not mandatory. [ctrl-alt-o]

values:
/wiki/Use_case
View the content page [ctrl-alt-c]
c

values: Discussion about the content page [ctrl-alt-t]

values: p-namespaces navigation vectorTabs p-namespaces-label

values:
p-variants
navigation
vectorMenu emptyPortlet
p-variants-label

values:
/w/index.php?title=Use_case&action=edit
Edit this page [ctrl-alt-e]
e

values: Past revisions of this page [ctrl-alt-h]

values: p-views navigation vectorTabs p-views-label

values:
p-cactions
navigation
vectorMenu emptyPortlet
p-cactions-label

values:
mw-wiki-logo
/wiki/Main_Page
Visit the main page

values:
/wiki/Main_Page
Visit the main page [ctrl-alt-z]
z

values: Featured content – the best of Wikipedia

values: Find background information on current events

values:
/wiki/Special:Random
Load a random article [ctrl-alt-x]
x

values: portal navigation p-navigation p-navigation-label

values: Guidance on how to use and edit Wikipedia

values: About the project, what you can do, where to find things

values: A list of recent changes in the wiki [ctrl-alt-r]

values: portal navigation p-interaction p-interaction-label

values: List of all English Wikipedia pages containing links to this page [ctrl-alt-j]

values: Recent changes in pages linked from this page [ctrl-alt-k]

values:
/wiki/Wikipedia:File_Upload_Wizard
Upload files [ctrl-alt-u]
u

values:
interlanguage-link interwiki-af
display: none;

values: حالة الاستخدام (هندسة البرمجيات) – Arabic

values:
interlanguage-link interwiki-ca
display: none;

values:
interlanguage-link interwiki-cs
display: none;

values:
https://da.wikipedia.org/wiki/Use_case
Use case – Danish
da
da
interlanguage-link-target

values:
interlanguage-link interwiki-da
display: none;

values: مورد استفاده – Persian

values:
interlanguage-link interwiki-fa
display: none;

values: 유스 케이스 – Korean

values:
interlanguage-link interwiki-it
display: none;

values: תרחיש שימוש – Hebrew

values:
interlanguage-link interwiki-he
display: none;

values:
https://nl.wikipedia.org/wiki/Use_case
Use case – Dutch
nl
nl
interlanguage-link-target

values:
interlanguage-link interwiki-nl
display: none;

values:
interlanguage-link interwiki-no
display: none;

values:
interlanguage-link interwiki-pl
display: none;

values: Сценарий использования – Russian

values:
https://sq.wikipedia.org/wiki/Use_case
Use case – Albanian
sq
sq
interlanguage-link-target

values:
interlanguage-link interwiki-sq
display: none;

values:
interlanguage-link interwiki-sk
display: none;

values:
interlanguage-link interwiki-fi
display: none;

values:
interlanguage-link interwiki-sv
display: none;

values:
interlanguage-link interwiki-tr
display: none;

values: Сценарій використання – Ukrainian

values:
interlanguage-link interwiki-uk
display: none;

values:
https://vi.wikipedia.org/wiki/Use_case
Use case – Vietnamese
vi
vi
interlanguage-link-target

values:
interlanguage-link interwiki-vi
display: none;

values: All languages (initial selection from common choices by you and others)

values: /static/images/wikimedia-button-1.5x.png 1.5x, /static/images/wikimedia-button-2x.png 2x

values: /static/images/poweredby_mediawiki_132x47.png 1.5x, /static/images/poweredby_mediawiki_176x62.png 2x

values:
suggestions
display: none; font-size: 13px;

values: mediawiki ltr sitedir-ltr mw-hide-empty-elt ns-0 ns-subject page-Use_case rootpage-Use_case skin-vector action-view


text:
Lying in state
From Wikipedia, the free encyclopedia
Jump to: navigation, search
For the band, see Lying in States.
Philip IV of France lying in state
Mahatma Gandhi lying in state
Lying in state is the tradition in which the body of a dead official is placed in a state building, either outside or inside a coffin, to allow the public to pay their respects. It traditionally takes place in the principal government building of a country, state, or city. While the practice differs among countries, a viewing in a location other than the principal government building may be referred to as lying in repose.[1]
Contents
[hide]
1 Canada
2 North Korea
3 Russia
4 Singapore
5 South Africa
6 United Kingdom
7 United States
7.1 Lain in state
7.2 Lain in honor
7.3 Lain in repose
7.4 States and cities
8 Vatican City
9 Coptic Patriarchate
10 Other notable funerals
11 See also
12 References
Canada[edit]
In Canada, official lying in state is a part of a state funeral, an honor generally reserved for former Governors General and former Prime Ministers. It is held in the Centre Block of Parliament Hill, in the national capital, Ottawa, Ontario. Ex-governors general lie in state in the Senate Chamber while former prime ministers lie in the Hall of Honour. During the period of lying in state, the coffins are flanked at each corner by a Guard of honour, made up of four members drawn from the Canadian Forces and Royal Canadian Mounted Police, as well as members of the Governor General's Foot Guards for former governors general, and guards from the parliamentary security forces for former prime ministers. Guards stand at each corner with heads bowed and weapons inverted (resting on Arms reversed) with their backs turned towards the casket.
Provinces may also mount state funerals and have a lying in state for a distinguished former resident. For instance, Maurice Richard, nationally known hockey player, was given a state funeral by the province of Quebec when he died in 2000; his coffin lay in state at the Molson Centre.[2] This process was repeated for fellow Canadiens legend Jean Béliveau in December 2014.
Municipalities may offer civic funerals to prominent deceased current or former politicians.
North Korea[edit]
In North Korea, the body of the late leader Kim Jong-il was displayed in a glass coffin surrounded with red flowers at the Kumsusan Memorial Palace in Pyongyang prior to his funeral, which began and ended at the palace. An honor guard armed with AK-47s was present. Jong-il's father Kim Il-sung, the founding president, is on display elsewhere in the palace.[3]
Russia[edit]
This section needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. (January 2013) (Learn how and when to remove this template message)
In Russia, during the time of the Soviet Union (1917–1991), the state funerals of the most senior political and military leaders, such as Vladimir Lenin, Joseph Stalin, Leonid Brezhnev, Yuri Andropov, and Konstantin Chernenko all followed the same basic outline. They took place in Moscow, beginning with a public lying in state of the deceased in the House of the Unions, and ending with an interment at Red Square.
For the lying in state at the House of the Unions, the coffin would be placed on display in the Column Hall, which would be decorated by flowers, numerous red flags and other communist symbols. The mourners, which usually would be brought in by the thousands, shuffled up a marble staircase beneath chandeliers draped in black gauze. On the stage at the left side of the Column Hall, a full orchestra in black tailcoats played classical music. The deceased's embalmed body, dressed in a black suit, white shirt and a tie, was displayed in an open coffin on a catafalque banked with carnations, red roses and tulips, facing the queue of mourners. A small guard of honour would be in attendance in the background. At the right side of the hall, seats were placed for guests of honour, with the front row reserved for the dead leader's family.
On the day of the funeral, a military funeral parade would take place during which the coffin would be conveyed from the House of the Unions to Red Square where burial would take place. Lenin and Stalin were placed inside the Lenin Mausoleum, while Brezhnev, Andropov, and Chernenko were interred in individual graves in the Kremlin Wall Necropolis.
Singapore[edit]
At state funerals in Singapore, the national flag is put on the coffin. The vigil guard may be deployed during the public lying in state of the deceased person at Parliament House. The deployment of the vigil guard is the highest form of respect accorded by the nation to the deceased. Similar to British traditions, the vigil guard is composed of groups of five commissioned officers from the Singapore Armed Forces (SAF) and Singapore Police Force (SPF) who stand guard around the clock in shifts of 30 minutes. One of the five officers stands facing outward at each of the four corners of the casket, while the fifth and most senior one stands in front and faces inward. Their heads are bowed and their ceremonial swords are inverted.[4]
Vigil guards were stationed at the public lying in state of Goh Keng Swee in May 2010,[5] Lee Kuan Yew in March 2015 [6] as well as S R Nathan in August 2016. [7]
South Africa[edit]
Nelson Mandela was the first democratically elected president to lie in state in South Africa.[citation needed] The event took place at the Union Buildings, the same site where he was inaugurated as the President of South Africa on May 10, 1994. The body of Mandela was lying in State for three days, starting on Wednesday, December 11, 2013 and ending Friday, December 13. The body was viewed by thousands of South Africans before it was airlifted to Qunu in the Eastern Cape where Mandela was buried on December 15, 2013.
United Kingdom[edit]
See also: State funerals in the United Kingdom and Vigil of the Princes
In state and ceremonial funerals in the United Kingdom, the lying-in-state takes place in Westminster Hall. The coffin is placed on a catafalque and is guarded, around the clock, by detachments, each of four men, from the following units:
Sovereign's Bodyguard
Her Majesty's Bodyguard of the Honourable Corps of Gentlemen-at-Arms
The Queen's Bodyguard of the Yeomen of the Guard
The Royal Company of Archers, The Queen's Bodyguard for Scotland
Household Cavalry
The Life Guards
The Blues and Royals (Royal Horse Guards and 1st Dragoons)
Foot Guards
Grenadier Guards
Coldstream Guards
Scots Guards
Irish Guards
Welsh Guards
Each unit mans the guard for a total of six hours, with each detachment standing post for twenty minutes. The four men stand at each corner with heads bowed and weapons inverted; their backs are turned towards the coffin.
On two occasions, the guard has been mounted by four male members of the Royal Family. At the lying in state of King George V in 1936, the guard was mounted by his four sons King Edward VIII, the Duke of York (George VI), the Duke of Gloucester and the Duke of Kent. For Queen Elizabeth The Queen Mother's lying-in-state in 2002, the guard was mounted by her four grandsons, the Prince of Wales, the Duke of York, the Earl of Wessex, and Viscount Linley.[8]
United States[edit]
See also: State funerals in the United States
Representative Thaddeus Stevens lying in state in the Capitol rotunda on August 13, 1868. Because of his prominence as an abolitionist, members of the Butler Zouaves, an African-American company of the District of Columbia, served as honor guards. A plaster statue of President Abraham Lincoln, likely submitted for a commission, was credited to Henry J. Ellicott.
John J. Pershing saluting the Unknown Soldier of World War I, who lay in state in the Capitol rotunda on November 9, 1921.
Lyndon B. Johnson and members of Congress honor President John F. Kennedy, who lay in state in the Capitol rotunda on November 24, 1963.
Richard Nixon and members of Congress honor Lyndon B. Johnson who lay in state in the Capitol rotunda on January 24, 1973.
The U.S. Joint Service Color Guard and members of Congress honor President Ronald Reagan, who lay in state in the Capitol rotunda on June 10, 2004.
Dick Cheney and members of Congress honor President Gerald Ford, who lay in state in the Capitol rotunda on December 30, 2006.
Lying in state is the rare honor granted by the United States to a deceased official whereby his or her remains are placed in the rotunda of the United States Capitol in Washington, D.C., for public viewing. The casket is guarded by members of the armed forces. By regulation and custom, only Presidents, military commanders, and members of Congress are granted the honor of lying in state. Except for Presidents and former Presidents, the honor is not automatic. Not all those entitled to the honor have it accepted by their survivors. The first leader to receive this honor was Henry Clay, former Speaker of the House of Representatives, when he died in 1852. Since then, the honor has been extended to 29 people, including eleven Presidents.
The process of lying in state at the Capitol is as follows. The coffin or casket is usually placed on a catafalque, usually the Lincoln catafalque, so named as it was constructed for lying in state upon the death of Abraham Lincoln, after his assassination in 1865. The casket is guarded at each of its corners by a serviceperson from each of the branches of the armed forces. In contrast to the practice in the United Kingdom and other countries of the Commonwealth, guards at the Capitol face the casket, hold their rifles with their right hand, and keep the rifle butt resting on the floor. After the viewing and ceremony at the Capitol, the remains are taken to the burial location.
Lain in state[edit]
1852 – Henry Clay, long-serving Senator and Representative, Secretary of State, Speaker of the House, and three-time presidential candidate
1865 – President Abraham Lincoln, assassinated in office
1868 – Thaddeus Stevens, Representative from Pennsylvania
1874 – Charles Sumner, Senator from Massachusetts
1875 – Vice President Henry Wilson, served under Grant, died in office
1881 – President James Garfield, assassinated in office
1886 – John A. Logan, Senator from Illinois
1901 – President William McKinley, assassinated while in office
1909 – Pierre L'Enfant – although he died in 1825, his remains were disinterred; he was honored by lying in state before reinterment at Arlington National Cemetery
1917 – Admiral George Dewey, Admiral of the Navy
1921 – The Unknown Soldier for World War I
1923 – President Warren Harding, died in office
1930 – President William Howard Taft, President 1909–13, also Chief Justice 1921–30
1948 – John J. Pershing, General of the Armies of the United States during World War I and after
1953 – Robert A. Taft, U.S. Senator and Majority Leader
1958 – The Unknown Soldiers for World War II and the Korean War
1963 – President John F. Kennedy, assassinated in office
1964 – General Douglas MacArthur, General of the Army
1964 – President Herbert Hoover, serving 1929–33
1969 – President Dwight Eisenhower, President 1953–1961, Supreme Allied Commander during World War II
1969 – Everett Dirksen, Illinois Senator, Senate Minority Leader 1959–1969
1972 – J. Edgar Hoover, FBI Director 1929–1972
1973 – President Lyndon B. Johnson, President 1963–1969
1978 – Hubert Humphrey, Vice President 1965–1969, Minnesota Senator
1984 – The Unknown Soldier for the Vietnam War (later identified as 1st. Lt. Michael J. Blassie)
1989 – Claude Pepper, long-serving Senator and Representative
2004 – President Ronald Reagan, President 1981–1989
2006–07 – President Gerald Ford, President 1974–1977
2012 – Daniel Inouye, President pro tempore of the U.S. Senate, Senator from Hawaii, and recipient of the Medal of Honor[9][10]
Lain in honor[edit]
1998 – United States Capitol Police Officer Jacob Chestnut and Detective John Gibson, killed on duty
2005 – Rosa Parks, civil rights activist [11][12]
2018 – Billy Graham, Christian evangelist[13]
The United States Congress has created a similar—though not identical—privilege for distinguished Americans who do not qualify for a lying in state designation. In the process of "lying in honor," the honor guard in the Rotunda is provided by the Capitol Police or another suitable source. [14][15]
In 1998, Chestnut and Gibson were killed while defending the Capitol against Russell Eugene Weston Jr. Congress approved their remains to lie in honor in the Rotunda. Chestnut was the first African American to lie in honor. In 2005, upon the death of civil rights activist Rosa Parks, Congress authorized her remains to lie in honor at the Rotunda; Parks was the second African American and the first woman to lie in honor in the Capitol Rotunda.[11] Graham was the first religious leader to be honored in this way.[16]
Lain in repose[edit]
Supreme Court Justices "lie in repose" in the Great Hall of the United States Supreme Court Building.
1974 – Chief Justice Earl Warren
1993 – Justice Thurgood Marshall
1995 – Chief Justice Warren E. Burger
1997 – Justice William J. Brennan, Jr.
1999 – Justice Harry A. Blackmun
2005 – Chief Justice William H. Rehnquist, the first so-honored to have died in office.
2016 – Justice Antonin Scalia
States and cities[edit]
Some U.S. states and cities extend similar honors. For example, in the state of Hawaii, three people have been laid in state at the Hawaii State Capitol, among which include famous Hawaiian singer Israel Kamakawiwoʻole upon his death in 1997, and the aforementioned Daniel Inouye, President pro tempore of the U.S. Senate and Senator from Hawaii.
In the City of San Francisco, California, Mayor Ed Lee laid in state at the Rotunda of San Francisco City Hall after his death in office in 2017.
Vatican City[edit]
Pope John Paul II's body lying in state.
A deceased pope customarily lies in state in the chapel of the Apostolic Palace and then in St. Peter's Basilica, between the holding of a Mass of Visitation and a Mass of Requiem.[citation needed] The funeral of Pope John Paul II was an example of this custom.
Coptic Patriarchate[edit]
The Coptic Orthodox Church of Alexandria has a tradition of mummifying the deceased pope and placing his body on his throne to enable church followers to have a farewell look at him for a short period of time. This tradition is one of the ways that ancient Egyptian rituals have survived in the Egyptian church. [17]
Other notable funerals[edit]
Death and funeral of Josip Broz Tito
Death and funeral of Corazon Aquino
Death and state funeral of Omar Bongo
Death and state funeral of Pierre Trudeau
Death and state funeral of Lech Kaczyński and Maria Kaczyńska
See also[edit]
Caisson
Death and state funeral of Ronald Reagan
Catafalque
Death and funeral of Richard Nixon
Funeral train
Lying in repose
Lincoln Catafalque
Missing man formation
Riderless horse
State funeral
State funeral of John F. Kennedy
State funerals in the United States
Vigil of the Princes
References[edit]
Jump up ^ [1] Archived June 11, 2007, at the Wayback Machine.
Jump up ^ "Rocket to get state funeral". CBC News. May 28, 2000.
Jump up ^ "Kim's body on show in North Korea amid mass mourning". AFP. The West Australian. Archived from the original on 3 January 2012. Retrieved 3 January 2012.
Jump up ^ Cheong, Danson (4 April 2015). "'An honour to stand vigil for Mr Lee Kuan Yew'". The Straits Times. Retrieved 21 March 2016.
Jump up ^ "Of state funerals and state-assisted funerals". Public Opinion.
Jump up ^ "Vigil guard, highest form of respect, accorded to Lee Kuan Yew during lying in state". Channel News Asia.
Jump up ^ "Vigil guards to be mounted for S R Nathan's Lying-in-State". Channel News Asia.
Jump up ^ [2] Archived July 31, 2007, at WebCite
Jump up ^ "Senator Inouye Lying in State". US Architect of the Capitol. December 19, 2012. Retrieved 2018-02-28.
Jump up ^ "Individuals Who Have Lain in State or in Honor". History, Art & Archives – United States House of Representatives. Retrieved 2018-02-28.
^ Jump up to: a b "Civil Rights Pioneer Rosa Parks Lies in Honor in Capitol Rotunda". Democracy Now!. Retrieved 2013-12-05.
Jump up ^ "Lying in State | Architect of the Capitol | United States Capitol". Aoc.gov. Retrieved 2013-12-05.
Jump up ^ "Billy Graham's body to 'lie in honor' at U.S. Capitol". charlotteobserver. Retrieved 2018-02-22.
Jump up ^ Those Who Have Lain In State or In Honor in the Capitol Rotunda, US Architect of the Capitol.
Jump up ^ Memorial or Funeral Services in the Capitol Rotunda (PDF), U.S. Senate Historical Office from the Architect of the Capitol.
Jump up ^ O'Keefe, Ed (February 22, 2018). "Billy Graham to lie in honor at the U.S. Capitol". The Washington Post. Retrieved 2018-02-28.
Jump up ^ Boulos Ayad Ayad, Phd: "Ancient Egyptian Civilization and the Coptic Church", Coptic Church Review, Volume 9, Number 4
Retrieved from "https://en.wikipedia.org/w/index.php?title=Lying_in_state&oldid=837270294"
Categories:
Death customs
State ritual and ceremonies
Hidden categories:
Webarchive template wayback links
Webarchive template webcite links
Articles needing additional references from January 2013
All articles needing additional references
All articles with unsourced statements
Articles with unsourced statements from September 2015
Articles with unsourced statements from November 2013
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
Namespaces
Article
Talk
Variants
Views
Read
Edit
View history
More
Search
Navigation
Main page
Contents
Featured content
Current events
Random article
Donate to Wikipedia
Wikipedia store
Interaction
Help
About Wikipedia
Community portal
Recent changes
Contact page
Tools
What links here
Related changes
Upload file
Special pages
Permanent link
Page information
Wikidata item
Cite this page
Print/export
Create a book
Download as PDF
Printable version
Languages
Català
Dansk
Deutsch
Español
Italiano
Nederlands
Norsk
Português
Simple English
Svenska
3 more
Edit links
This page was last edited on 19 April 2018, at 19:37.
Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.
Privacy policy
About Wikipedia
Disclaimers
Contact Wikipedia
Developers
Cookie statement
Mobile view
Enable previews

key: html

type: local

value: div

attrs: id class

values: mw-page-base noprint

values: mw-head-base noprint

value: a

attrs: id class lang

values: firstHeading firstHeading en

values: siteSub noprint

values: jump-to-nav mw-jump

attrs: href title

attrs: role class

values:
note
hatnote navigation-not-searchable

value: img

attrs: alt src width height class srcset data-file-width data-file-height

attrs: href class

values:
/wiki/Canadian_Forces
mw-redirect
Canadian Forces

attrs: alt src width height srcset data-file-width data-file-height

values: Help:Introduction to referencing with Wiki Markup/1

values: plainlinks metadata ambox ambox-content ambox-Refimprove

values:
/wiki/Lenin_Mausoleum
mw-redirect
Lenin Mausoleum

values: This claim needs references to reliable sources. (September 2015)

values:
noprint Inline-Template Template-Fact
white-space:nowrap;

values:
/wiki/Westminster_Hall
mw-redirect
Westminster Hall

values:
/wiki/Life_Guards_(Britain)
mw-redirect
Life Guards (Britain)

values:
/wiki/Foot_Guards
mw-redirect
Foot Guards

values:
/wiki/Royal_Family
mw-redirect
Royal Family

values:
/wiki/Henry,_Duke_of_Gloucester
mw-redirect
Henry, Duke of Gloucester

values:
/wiki/George,_Duke_of_Kent
mw-redirect
George, Duke of Kent

values:
/wiki/Capitol_rotunda
mw-redirect
Capitol rotunda

values:
/wiki/Tomb_of_the_Unknowns
mw-redirect
Tomb of the Unknowns

values:
/wiki/United_States_armed_forces
mw-redirect
United States armed forces

values: Speaker of the United States House of Representatives

values:
/wiki/Lincoln_catafalque
mw-redirect
Lincoln catafalque

values:
/wiki/Lincoln_Assassination
mw-redirect
Lincoln Assassination

values:
/wiki/James_Garfield
mw-redirect
James Garfield

values:
/wiki/Pierre_L%27Enfant
mw-redirect
Pierre L'Enfant

values:
/wiki/Warren_Harding
mw-redirect
Warren Harding

values:
/wiki/John_F._Kennedy_assassination
mw-redirect
John F. Kennedy assassination

values:
/wiki/Dwight_Eisenhower
mw-redirect
Dwight Eisenhower

values: President pro tempore of the United States Senate

values: United States Capitol shooting incident (1998)

values:
/wiki/African_American
mw-redirect
African American

values:
/wiki/Supreme_Court_Justice
mw-redirect
Supreme Court Justice

values:
/wiki/William_J._Brennan,_Jr.
mw-redirect
William J. Brennan, Jr.

values:
/wiki/William_H._Rehnquist
mw-redirect
William H. Rehnquist

values:
/wiki/San_Francisco,_California
mw-redirect
San Francisco, California

values: Mass of Visitation (page does not exist)

values:
/wiki/Mass_of_Requiem
mw-redirect
Mass of Requiem

values: This claim needs references to reliable sources. (November 2013)

values:
/wiki/Death_of_Josip_Broz_Tito
mw-redirect
Death of Josip Broz Tito

values: Death and state funeral of Pierre Trudeau

values:
/wiki/Limbers_and_caissons_(military)
mw-redirect
Limbers and caissons (military)

values: Death and state funeral of Ronald Reagan

values: Category:Webarchive template wayback links

values: Category:Webarchive template webcite links

values: Category:Articles needing additional references from January 2013

values: Category:All articles needing additional references

values: Category:All articles with unsourced statements

values: Category:Articles with unsourced statements from September 2015

values: Category:Articles with unsourced statements from November 2013

values: Discussion about edits from this IP address [ctrl-alt-n]

values: A list of edits made from this IP address [ctrl-alt-y]

values: You are encouraged to create an account and log in; however, it is not mandatory

values: You're encouraged to log in; however, it's not mandatory. [ctrl-alt-o]

values:
/wiki/Lying_in_state
View the content page [ctrl-alt-c]
c

values: Discussion about the content page [ctrl-alt-t]

values: p-namespaces navigation vectorTabs p-namespaces-label

values:
p-variants
navigation
vectorMenu emptyPortlet
p-variants-label

values: Past revisions of this page [ctrl-alt-h]

values: p-views navigation vectorTabs p-views-label

values:
p-cactions
navigation
vectorMenu emptyPortlet
p-cactions-label

values:
mw-wiki-logo
/wiki/Main_Page
Visit the main page

values:
/wiki/Main_Page
Visit the main page [ctrl-alt-z]
z

values: Featured content – the best of Wikipedia

values: Find background information on current events

values:
/wiki/Special:Random
Load a random article [ctrl-alt-x]
x

values: portal navigation p-navigation p-navigation-label

values: Guidance on how to use and edit Wikipedia

values: About the project, what you can do, where to find things

values: A list of recent changes in the wiki [ctrl-alt-r]

values: portal navigation p-interaction p-interaction-label

values: List of all English Wikipedia pages containing links to this page [ctrl-alt-j]

values: Recent changes in pages linked from this page [ctrl-alt-k]

values:
/wiki/Wikipedia:File_Upload_Wizard
Upload files [ctrl-alt-u]
u

values: A list of all special pages [ctrl-alt-q]

values: Permanent link to this revision of the page

values: Link to connected data repository item [ctrl-alt-g]

values: Printable version of this page [ctrl-alt-p]

values:
interlanguage-link interwiki-da
display: none;

values: Esposizione pubblica della salma – Italian

values:
https://nl.wikipedia.org/wiki/Opbaren
Opbaren – Dutch
nl
nl
interlanguage-link-target

values:
interlanguage-link interwiki-simple
display: none;

values: mediawiki ltr sitedir-ltr mw-hide-empty-elt ns-0 ns-subject page-Lying_in_state rootpage-Lying_in_state skin-vector action-view


text:
Dell Parker
From Wikipedia, the free encyclopedia
Jump to navigation Jump to search
This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. (June 2015) (Learn how and when to remove this template message)
William Parker
Private Practice & Grey's Anatomy character
First appearance
Grey's Anatomy:
"The Other Side of This Life (Part 1)" 3x22
Private Practice:
"In Which We Meet Addison, a Nice Girl From Somewhere Else" 1x01
Last appearance
Grey's Anatomy:
"The Other Side of This Life (part 2)" 3x23
Private Practice:
"The End of a Beautiful Friendship" 3x23
Created by
Shonda Rhimes
Portrayed by
Chris Lowell
Information
Aliases
Dell
Gender
Male
Occupation
Midwife
Registered Nurse
Receptionist
Spouse(s)
Heather Parker (deceased)
Children
Betsy Parker (daughter with Heather)
Relatives
Wendell Parker (grandfather)
William Parker, more commonly known as Dell Parker, is a character on the Grey's Anatomy spin-off, Private Practice.[1] He was portrayed by actor Chris Lowell and appeared from the first through third seasons. Dell was the receptionist at the Oceanside Wellness Group as well as a qualified nurse, training to be a mid-wife, helping out the doctors with various tasks. Dell was frequently shown to be concerned with the health of younger patients, which is likely related to his abuse as a child, as well as his own young daughter. The character died following injuries sustained in a car crash.[2]
Contents
[hide]
1 Storylines
1.1 Season 1
1.2 Season 2
1.3 Season 3
2 References
3 External links
Storylines[edit]
Season 1[edit]
Dell was abused as a child, which allows him to relate to patients of the practice who have similar experiences. In the first season, Dell falls in love with Naomi Bennett, his boss, despite the fact she later becomes involved with Sam Bennett, her former husband. In the season one finale, Dell finally expresses his feelings and tries to kiss Naomi.[3]
Season 2[edit]
In the season two premiere, Dell tries to help Naomi hide the practice's budding financial struggles, under the pretenses of "going green," but does so without her knowledge.[4] However, believing he wants to talk to her regarding his crush on her, Naomi continually ignores his pleas to discuss the matter, forcing Dell to concede and quit his job.
After leaving his job at the Oceanside Wellness Group, Dell works as a nurse at St. Ambrose Hospital.[5] Upon learning this, Naomi tries to convince Dell to return to the practice without much luck. After a pep talk from Addison, Dell wishes to return to the practice as long as a list of demands are met, one of which states that he is to be exempt from wearing pink scrubs. Sam, the head of the practice at the time, refuses to rehire him. This forces Naomi to fight for his reinstatement to which Sam finally agrees.
Dell later ends up arguing with Addison, who has since become the head of the practice, over whether or not he should have his own office; but he eventually ends up setting one aside for himself without permission. However, Addison does not punish him and allows him to keep the office when it is revealed that he has a six-year-old daughter, Betsy, from an unsuccessful relationship with Heather when he was seventeen; and he was just trying to impress his daughter.
Dell enrolled as a student in the South Bay School of Holistic Midwifery and Family Nursing. He earned credit towards his degree in midwifery by assisting staff doctors with obstetrical exams and childbirths. Dell's hobbies included surfing during his lunch breaks.
When Heather gets a promotion at work, she talks to Dell, informing him the promotion is in St. Louis. Dell does not want this to happen, and they fight about it. Later on, when Dell goes to talk to her, he finds her apartment empty, and Betsy gone.
Season 3[edit]
Dell married Heather, and most of the group at the Practice did not approve of it. He later yelled at Violet and Naomi due to their opposition of his marriage.
One night when Dell was heading out for work, his home exploded. Betsy escapes with minor injuries, but Heather received third degree burns on her body. Later on, the explosion was revealed to have been caused by Heather cooking crystal meth on the stove. After this revelation, Dell was furious and told Heather to go die and suffer a miserable death for putting their daughter in danger, then proceeded to not allow Betsy see her mother. Later in the hospital that night, Heather died due to her injuries, never having the chance to say good-bye to Dell or Betsy.
Dell later befriended Naomi and Sam's daughter Maya, who had gotten pregnant and didn't have her mother's support. Dell supported Maya when she decided to marry Dink, the father of her baby, and later helped them out during her pregnancy. When Maya goes into labor, she calls Dell who picks her up and drives her to the hospital. They are involved in a car crash and Maya is in a critical state, as well as her baby. With everything going on with Maya and the baby, nobody checks on Dell, who suddenly passes out and is revealed to have an initially undetected brain hemorrhage. Naomi will not let Amelia out of Maya's spinal surgery to fix Dell, and Charlotte and Amelia eventually operate on him, but during surgery he goes into cardiac arrest and Charlotte and Amelia were not able to resuscitate him on the table.[6]
References[edit]
Jump up ^ Michael Grossman (director), Shonda Rhimes (writer). Grey's Anatomy: Season 3, Episode 22 "The Other Side of This Life (Part 1)"
Jump up ^ Jeannot Szwarc (director), Debora Cahn (writer). Private Practice: Season 3, Episode 23 "The End of a Beautiful Friendship"
Jump up ^ Wendey Stanzler (director), Ayanna Floyd (writer). Season 1, Episode 9 "In Which Dell Finds His Flight"
Jump up ^ Mark Tinker (director), Shonda Rhimes & Marti Noxon (writers). Season 2, Episode 1 "A Family Thing"
Jump up ^ Helen Shaver (director), Ayanna A. Floyd (writer). Season 2, Episode 3 "Nothing to Talk About"
Jump up ^ Jeannot Szwarc (director), Debora Cahn (writer). Season 3, Episode 23 "The End of a Beautiful Friendship"
External links[edit]
ABC Bio of Dell Parker
hide
v
t
e
Private Practice
Episodes
Season 1
2
3
4
"Did You Hear What Happened to Charlotte King?"
5
6
Characters
Addison Montgomery
Pete Wilder
Naomi Bennett
Cooper Freedman
Charlotte King
Dell Parker
Sheldon Wallace
Amelia Shepherd
Sam Bennett
Violet Turner
See also
Grey's Anatomy
Retrieved from "https://en.wikipedia.org/w/index.php?title=Dell_Parker&oldid=814503718"
Categories:
Fictional medical personnel
Private Practice characters
Fictional characters introduced in 2007
Hidden categories:
Articles needing additional references from June 2015
All articles needing additional references
Pages using infobox character with unknown parameters
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
Namespaces
Article
Talk
Variants
Views
Read
Edit
View history
More
Search
Navigation
Main page
Contents
Featured content
Current events
Random article
Donate to Wikipedia
Wikipedia store
Interaction
Help
About Wikipedia
Community portal
Recent changes
Contact page
Tools
What links here
Related changes
Upload file
Special pages
Permanent link
Page information
Wikidata item
Cite this page
Print/export
Create a book
Download as PDF
Printable version
Languages
Italiano
Português
Edit links
This page was last edited on 9 December 2017, at 05:41.
Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.
Privacy policy
About Wikipedia
Disclaimers
Contact Wikipedia
Developers
Cookie statement
Mobile view
Enable previews

values: mw-page-base noprint

values: mw-head-base noprint

values: firstHeading firstHeading en

values: siteSub noprint

values: mw-jump-link #mw-head

values: mw-jump-link #p-search

value: td

value: b

values: Help:Introduction to referencing with Wiki Markup/1

value: span

value: i

value: small

values: plainlinks metadata ambox ambox-content ambox-Refimprove

values:
infobox
width:22em;border-spacing: 2px 5px;

values:
/wiki/Addison_Forbes_Montgomery
mw-redirect
Addison Forbes Montgomery

values:
reflist mw-references-wrap
list-style-type: decimal;

values: nowraplinks hlist collapsible autocollapse navbox-inner mw-collapsible mw-made-collapsible

values: Category:Fictional characters introduced in 2007

values: Category:Articles needing additional references from June 2015

values: Category:All articles needing additional references

values: Category:Pages using infobox character with unknown parameters

values: Discussion about edits from this IP address [ctrl-alt-n]

values: A list of edits made from this IP address [ctrl-alt-y]

values: You are encouraged to create an account and log in; however, it is not mandatory

values: You're encouraged to log in; however, it's not mandatory. [ctrl-alt-o]

values:
/wiki/Dell_Parker
View the content page [ctrl-alt-c]
c

values: Discussion about the content page [ctrl-alt-t]

values: p-namespaces navigation vectorTabs p-namespaces-label

values:
p-variants
navigation
vectorMenu emptyPortlet
p-variants-label

values: Past revisions of this page [ctrl-alt-h]

values: p-views navigation vectorTabs p-views-label

values:
p-cactions
navigation
vectorMenu emptyPortlet
p-cactions-label

values:
mw-wiki-logo
/wiki/Main_Page
Visit the main page

values:
/wiki/Main_Page
Visit the main page [ctrl-alt-z]
z

values: Featured content – the best of Wikipedia

values: Find background information on current events

values:
/wiki/Special:Random
Load a random article [ctrl-alt-x]
x

values: portal navigation p-navigation p-navigation-label

values: /static/images/wikimedia-button-1.5x.png 1.5x, /static/images/wikimedia-button-2x.png 2x

values: /static/images/poweredby_mediawiki_132x47.png 1.5x, /static/images/poweredby_mediawiki_176x62.png 2x

values:
suggestions
display: none; font-size: 13px;

values: mediawiki ltr sitedir-ltr mw-hide-empty-elt ns-0 ns-subject page-Dell_Parker rootpage-Dell_Parker skin-vector action-view


text:
2018 Chinese Grand Prix
From Wikipedia, the free encyclopedia
Jump to navigation Jump to search
2018 Chinese Grand Prix
Race 3 of 21 in the 2018 Formula One World Championship
← Previous race Next race →
Layout of the Shanghai International Circuit
Race details[1]
Date
15 April 2018
Official name
Formula 1 2018 Heineken Chinese Grand Prix
Location
Shanghai International Circuit, Shanghai, China
Course
Permanent racing facility
Course length
5.451 km (3.387 mi)
Distance
56 laps, 305.066 km (189.559 mi)
Pole position
Driver
Sebastian Vettel
Ferrari
Time
1:31.095
Fastest lap
Driver
Daniel Ricciardo Red Bull Racing-TAG Heuer
Time
1:35.785 on lap 55
Podium
First
Daniel Ricciardo
Red Bull Racing-TAG Heuer
Second
Valtteri Bottas
Mercedes
Third
Kimi Räikkönen
Ferrari
Lap leaders[show]
The 2018 Chinese Grand Prix (formally known as the Formula 1 2018 Heineken Chinese Grand Prix) was a Formula One motor race that took place on 15 April 2018 at the Shanghai International Circuit in Shanghai, China. The race was the third round of the 2018 FIA Formula One World Championship,[2] and marked the fifteenth time that the Chinese Grand Prix has been run as a round of the Formula One World Championship.
Mercedes driver Lewis Hamilton was the defending race winner.[3] Sebastian Vettel entered the round with a seventeen-point lead over Hamilton in the World Drivers' Championship. His team, Ferrari, led Mercedes by ten points in the World Constructors' Championship. Vettel qualified on pole position,[4] and in doing so recorded Ferrari's first pole position in China in fourteen years. Daniel Ricciardo won the race ahead of Valtteri Bottas and Kimi Räikkönen.[5] Vettel's championship lead was cut to nine points when he finished in eighth place, the result of contact with Max Verstappen late in the race.
Contents
[hide]
1 Report
1.1 Practice
1.2 Qualifying
1.3 Race
2 Classification
2.1 Qualifying
2.2 Race
2.3 Championship standings after the race
3 References
4 External links
Report[edit]
Practice[edit]
Lewis Hamilton was quickest in FP1 and FP2. Sebastian Vettel was quickest in FP3. During FP3, Daniel Ricciardo's turbo failed, requiring a full rebuild.
Qualifying[edit]
Daniel Ricciardo's pit crew, still frantically assembling his Red Bull engine and car as qualifying began, were able to get his car out in Q1 with just over three minutes left in the session. With his first and only possible hot lap in Q1, he finished the session in P13. Charles Leclerc, meanwhile, spun his Sauber, and failed to make it out of Q1. Marcus Ericsson was given a 5 place grid penalty for the race, and 3 points on his super license, for ignoring the double yellow flags waved for Leclerc. After qualifying P6 in Bahrain, Pierre Gasly also failed to make it out of Q1.
Ferrari locked out the front row of the grid for the second consecutive race, the first time since 2006 that the team had achieved this feat. Sebastian Vettel qualified on pole position with a time of 1:31.095, a new track record. Mercedes locked out the second row of the grid, and Red Bull the third.
Race[edit]
Polesitter Sebastian Vettel got away well at the start, however his team mate Kimi Räikkönen lost positions, being overtaken by Bottas in Turn 1, and then Verstappen a few corners later.. Hamilton fell back to 5th, whilst Ricciardo held 6th. After the first pit stops, Bottas managed to undercut Vettel and subsequently overtook Kimi Räikkönen, who had not yet stopped, for the lead, around the outside in Turn 1. After Bottas blocked off Räikkönen, Vettel took advantage to take second place.
On Lap 30, the Toro Rosso cars of Brendon Hartley and Pierre Gasly collided at the hairpin. Gasly was awarded a 10 second penalty and the debris left on the track resulted in the safety car being brought out. This was a critical turning point for the race, as during the safety car period, both Red Bull cars pitted for fresh tyres on the same lap immediately. Mercedes had an opportunity to bring Hamilton in, but instead left him out to preserve track position. Bottas maintained the lead of the race at the safety car restart. Max Verstappen ran wide on Lap 39 whilst battling with Lewis Hamilton for third place, losing a position to Ricciardo, who had previously overtaken Räikkönen. Both Red Bulls then overtook Hamilton, two laps apart, and then Ricciardo overtook Vettel for P2. On Lap 43, Max Verstappen shunted Sebastian Vettel off the track at the hairpin, resulting in both drivers spinning off the track and Vettel losing positions, due to a damaged floor. Verstappen was awarded a 10 second penalty for the incident. On Lap 45 Ricciardo overtook Bottas for the lead of the race, which he would retain until the chequered flag. On the penultimate lap, Vettel was overtaken by Fernando Alonso meaning he would finish in P8.
Riccardo's many overtakes would be hailed as a stunning drive, and the race would be regarded as one of his best ever.
Classification[edit]
Qualifying[edit]
Pos.
Car
no.
Driver
Constructor
Qualifying times
Final
grid
Q1
Q2
Q3
1
5 Sebastian Vettel Ferrari 1:32.171 1:32.385 1:31.095 1
2
7 Kimi Räikkönen Ferrari 1:32.474 1:32.286 1:31.182 2
3
77 Valtteri Bottas Mercedes 1:32.921 1:32.063 1:31.625 3
4
44 Lewis Hamilton Mercedes 1:33.283 1:31.914 1:31.675 4
5
33 Max Verstappen Red Bull Racing-TAG Heuer 1:32.932 1:32.809 1:31.796 5
6
3 Daniel Ricciardo Red Bull Racing-TAG Heuer 1:33.877 1:32.688 1:31.948 6
7
27 Nico Hülkenberg Renault 1:33.545 1:32.494 1:32.532 7
8
11 Sergio Pérez Force India-Mercedes 1:33.464 1:32.931 1:32.758 8
9
55 Carlos Sainz Jr. Renault 1:33.315 1:32.970 1:32.819 9
10
8 Romain Grosjean Haas-Ferrari 1:33.238 1:32.524 1:32.855 10
11
20 Kevin Magnussen Haas-Ferrari 1:33.359 1:32.986 11
12
31 Esteban Ocon Force India-Mercedes 1:33.585 1:33.057 12
13
14 Fernando Alonso McLaren-Renault 1:33.428 1:33.232 13
14
2 Stoffel Vandoorne McLaren-Renault 1:33.824 1:33.505 14
15
28 Brendon Hartley Scuderia Toro Rosso-Honda 1:34.013 1:33.795 15
16
35 Sergey Sirotkin Williams-Mercedes 1:34.062 16
17
10 Pierre Gasly Scuderia Toro Rosso-Honda 1:34.101 17
18
18 Lance Stroll Williams-Mercedes 1:34.285 18
19
16 Charles Leclerc Sauber-Ferrari 1:34.454 19
20
9 Marcus Ericsson Sauber-Ferrari 1:34.914 201
107% time: 1:38.622
Source:[4]
Notes
^1 – Marcus Ericsson was given a five-place grid penalty for ignoring yellow flags during qualifying.
Race[edit]
Pos.
No.
Driver
Constructor
Laps
Time/Retired
Grid
Points
1
3 Daniel Ricciardo Red Bull Racing-TAG Heuer 56 1:35:36.380 6 25
2
77 Valtteri Bottas Mercedes 56 +8.894 3 18
3
7 Kimi Räikkönen Ferrari 56 +9.637 2 15
4
44 Lewis Hamilton Mercedes 56 +16.985 4 12
5
33 Max Verstappen Red Bull Racing-TAG Heuer 56 +20.4361 5 10
6
27 Nico Hülkenberg Renault 56 +21.052 7 8
7
14 Fernando Alonso McLaren-Renault 56 +30.639 13 6
8
5 Sebastian Vettel Ferrari 56 +35.286 1 4
9
55 Carlos Sainz Jr. Renault 56 +35.763 9 2
10
20 Kevin Magnussen Haas-Ferrari 56 +39.594 11 1
11
31 Esteban Ocon Force India-Mercedes 56 +44.050 12
12
11 Sergio Pérez Force India-Mercedes 56 +44.725 8
13
2 Stoffel Vandoorne McLaren-Renault 56 +49.373 14
14
18 Lance Stroll Williams-Mercedes 56 +55.490 18
15
35 Sergey Sirotkin Williams-Mercedes 56 +58.241 16
16
9 Marcus Ericsson Sauber-Ferrari 56 +1:02.604 20
17
8 Romain Grosjean Haas-Ferrari 56 +1:05.296 10
18
10 Pierre Gasly Scuderia Toro Rosso-Honda 56 +1:06.3302 17
19
16 Charles Leclerc Sauber-Ferrari 56 +1:22.575 19
203
28 Brendon Hartley Scuderia Toro Rosso-Honda 51 Gearbox 15
Source:[6]
Notes
^1 – Max Verstappen originally finished in fourth place but had ten seconds added to his race time for causing an avoidable collision.
^2 – Pierre Gasly originally finished in fifteenth place but had ten seconds added to his race time for causing an avoidable collision.
^3 – Brendon Hartley retired from the race but was classified as he completed 90% of the winner's race distance.
Championship standings after the race[edit]
Drivers' Championship standings
Pos.
Driver
Points
1 Sebastian Vettel 54
2 Lewis Hamilton 45
3 Valtteri Bottas 40
3 4 Daniel Ricciardo 37
5 Kimi Räikkönen 30
Constructors' Championship standings
Pos.
Constructor
Points
1 1 Mercedes 85
1 2 Ferrari 84
1 3 Red Bull Racing-TAG Heuer 55
1 4 McLaren-Renault 28
5 Renault 25
References[edit]
Jump up ^ "Formula 1 2018 Chinese Grand Prix". formula1.com. Formula One World Championship Limited. Retrieved 8 April 2018.
Jump up ^ "FIA announces World Motor Sport Council decisions". Federation Internationale de l'Automobile. 6 December 2017. Archived from the original on 7 December 2017. Retrieved 8 April 2018.
Jump up ^ "2017 Chinese Grand Prix Race – Official Classification". FIA.com. Fédération Internationale de l'Automobile. 9 April 2017. Archived from the original on 9 April 2017. Retrieved 8 April 2018.
^ Jump up to: a b "Formula 1 2018 Heineken Chinese Grand Prix – Qualifying". Formula1.com. Formula One World Championship Limited. 14 April 2018. Retrieved 14 April 2018.
Jump up ^ "Daniel Ricciardo storms to Chinese Grand Prix win with sensational drive". abc.net.au. Australian Broadcasting Corporation. 15 April 2018. Retrieved 15 April 2018.
Jump up ^ "Formula 1 2018 Heineken Chinese Grand Prix – Race Result". Formula1.com. Formula One World Championship Limited. 15 April 2018. Retrieved 15 April 2018.
External links[edit]
Wikimedia Commons has media related to 2018 Chinese Grand Prix.
The race on the official Formula One website

Previous race:
2018 Bahrain Grand Prix FIA Formula One World Championship
2018 season Next race:
2018 Azerbaijan Grand Prix
Previous race:
2017 Chinese Grand Prix Chinese Grand Prix Next race:
2019 Chinese Grand Prix
show
v
t
e
« previous
Formula One Grands Prix (2010–18)
2018
AUS
BHR
CHN
AZE
ESP
MON
CAN
FRA
AUT
GBR
GER
HUN
BEL
ITA
SIN
RUS
JPN
USA
MEX
BRA
ABU
2017
AUS
CHN
BHR
RUS
ESP
MON
CAN
AZE
AUT
GBR
HUN
BEL
ITA
SIN
MAL
JPN
USA
MEX
BRA
ABU
2016
AUS
BHR
CHN
RUS
ESP
MON
CAN
EUR
AUT
GBR
HUN
GER
BEL
ITA
SIN
MAL
JPN
USA
MEX
BRA
ABU
2015
AUS
MAL
CHN
BHR
ESP
MON
CAN
AUT
GBR
HUN
BEL
ITA
SIN
JPN
RUS
USA
MEX
BRA
ABU
2014
AUS
MAL
BHR
CHN
ESP
MON
CAN
AUT
GBR
GER
HUN
BEL
ITA
SIN
JPN
RUS
USA
BRA
ABU
2013
AUS
MAL
CHN
BHR
ESP
MON
CAN
GBR
GER
HUN
BEL
ITA
SIN
KOR
JPN
IND
ABU
USA
BRA
2012
AUS
MAL
CHN
BHR
ESP
MON
CAN
EUR
GBR
GER
HUN
BEL
ITA
SIN
JPN
KOR
IND
ABU
USA
BRA
2011
BHR
AUS
MAL
CHN
TUR
ESP
MON
CAN
EUR
GBR
GER
HUN
BEL
ITA
SIN
JPN
KOR
IND
ABU
BRA
2010
BHR
AUS
MAL
CHN
ESP
MON
TUR
CAN
EUR
GBR
GER
HUN
BEL
ITA
SIN
JPN
KOR
BRA
ABU
Retrieved from "https://en.wikipedia.org/w/index.php?title=2018_Chinese_Grand_Prix&oldid=846866242"
Categories:
2018 Formula One races
Chinese Grand Prix
2018 in Chinese motorsport
April 2018 sports events in Asia
Hidden categories:
Pages using Timeline
Use dmy dates from April 2017
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
Namespaces
Article
Talk
Variants
Views
Read
Edit
View history
More
Search
Navigation
Main page
Contents
Featured content
Current events
Random article
Donate to Wikipedia
Wikipedia store
Interaction
Help
About Wikipedia
Community portal
Recent changes
Contact page
Tools
What links here
Related changes
Upload file
Special pages
Permanent link
Page information
Wikidata item
Cite this page
Print/export
Create a book
Download as PDF
Printable version
In other projects
Wikimedia Commons
Languages
Afrikaans
Azərbaycanca
Bosanski
Dansk
Deutsch
Ελληνικά
Español
Français
Galego
Hrvatski
Bahasa Indonesia
Italiano
Lietuvių
Magyar
Nederlands
日本語
Português
Română
Русский
Slovenščina
Suomi
Svenska
Türkçe
Українська
中文
16 more
Edit links
This page was last edited on 21 June 2018, at 10:42 (UTC).
Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.
Privacy policy
About Wikipedia
Disclaimers
Contact Wikipedia
Developers
Cookie statement
Mobile view
Enable previews

values: mw-page-base noprint

values: mw-head-base noprint

values: firstHeading firstHeading en

values: siteSub noprint

values: mw-jump-link #mw-head

values: mw-jump-link #p-search

value: th

attrs: colspan style

value: tr

value: tbody

value: table

values: font-size: 105%; text-align: center; background-color:#efefef;

values: list-style: none none; margin-left: 0px; text-align: center; font-size: 105%; margin-top: 0px; margin-bottom: 0px; line-height: inherit; display: none;

values:
NavFrame collapsed
border: none; padding: 0;
NavFrame1

values: width:22em;width: 27em; line-height: 1.5em;

values: Mercedes AMG High Performance Powertrains

values: Edit section: Championship standings after the race

values: border-collapse: collapse; padding: 0; border: 0; background:transparent; width:100%;

values:
reflist mw-references-wrap
list-style-type: decimal;

values: commons:Category:2018 Chinese Grand Prix

values: 2019 Chinese Grand Prix (page does not exist)

values:
/wiki/2018_Hungarian_Grand_Prix
mw-redirect
2018 Hungarian Grand Prix

values:
/wiki/2018_Belgian_Grand_Prix
mw-redirect
2018 Belgian Grand Prix

values:
/wiki/2018_Italian_Grand_Prix
mw-redirect
2018 Italian Grand Prix

values:
/wiki/2018_Singapore_Grand_Prix
mw-redirect
2018 Singapore Grand Prix

values:
/wiki/2018_Russian_Grand_Prix
mw-redirect
2018 Russian Grand Prix

values:
/wiki/2018_Japanese_Grand_Prix
mw-redirect
2018 Japanese Grand Prix

values:
/wiki/2018_United_States_Grand_Prix
mw-redirect
2018 United States Grand Prix

values:
/wiki/2018_Mexican_Grand_Prix
mw-redirect
2018 Mexican Grand Prix

values:
/wiki/2018_Brazilian_Grand_Prix
mw-redirect
2018 Brazilian Grand Prix

values:
/wiki/2018_Abu_Dhabi_Grand_Prix
mw-redirect
2018 Abu Dhabi Grand Prix

values: nowraplinks collapsible collapsed navbox-inner mw-collapsible mw-collapsed mw-made-collapsible

values: Category:April 2018 sports events in Asia

values: Discussion about edits from this IP address [ctrl-alt-n]

values: A list of edits made from this IP address [ctrl-alt-y]

values: You are encouraged to create an account and log in; however, it is not mandatory

values: You're encouraged to log in; however, it's not mandatory. [ctrl-alt-o]

values:
/wiki/2018_Chinese_Grand_Prix
View the content page [ctrl-alt-c]
c

values: Guidance on how to use and edit Wikipedia

values: About the project, what you can do, where to find things

values: A list of recent changes in the wiki [ctrl-alt-r]

values: portal navigation p-interaction p-interaction-label

values: List of all English Wikipedia pages containing links to this page [ctrl-alt-j]

values: Recent changes in pages linked from this page [ctrl-alt-k]

values:
/wiki/Wikipedia:File_Upload_Wizard
Upload files [ctrl-alt-u]
u

values: A list of all special pages [ctrl-alt-q]

values: Permanent link to this revision of the page

values: Link to connected data repository item [ctrl-alt-g]

values: Printable version of this page [ctrl-alt-p]

values: portal navigation p-wikibase-otherprojects p-wikibase-otherprojects-label

values:
interlanguage-link interwiki-af
display: none;

values:
interlanguage-link interwiki-az
display: none;

values:
interlanguage-link interwiki-bs
display: none;

values:
interlanguage-link interwiki-da
display: none;

values: Γκραν Πρι Κίνας 2018 (Φόρμουλα 1) – Greek

values:
interlanguage-link interwiki-el
display: none;

values: Anexo:Gran Premio de China de 2018 – Spanish

values: Grand Prix automobile de Chine 2018 – French

values:
interlanguage-link interwiki-gl
display: none;

values:
interlanguage-link interwiki-hr
display: none;

values: Grand Prix F1 Tiongkok 2018 – Indonesian

values:
interlanguage-link interwiki-it
display: none;

values:
interlanguage-link interwiki-lt
display: none;

values: 2018-as Formula–1 kínai nagydíj – Hungarian

values:
interlanguage-link interwiki-hu
display: none;

values: Grand Prix Formule 1 van China 2018 – Dutch

values:
interlanguage-link interwiki-nl
display: none;

values: Grande Prêmio da China de 2018 – Portuguese

values: Marele Premiu al Chinei din 2018 – Romanian

values:
interlanguage-link interwiki-ro
display: none;

values: Гран-при Китая 2018 года – Russian

values: Velika nagrada Kitajske 2018 – Slovenian

values:
interlanguage-link interwiki-sl
display: none;

values:
interlanguage-link interwiki-fi
display: none;

values:
interlanguage-link interwiki-sv
display: none;

values: Формула-1 — Гран-прі Китаю 2018 – Ukrainian

values:
interlanguage-link interwiki-uk
display: none;

values: All languages (initial selection from common choices by you and others)

values: mediawiki ltr sitedir-ltr mw-hide-empty-elt ns-0 ns-subject page-2018_Chinese_Grand_Prix rootpage-2018_Chinese_Grand_Prix skin-vector action-view