Software Engineering Seminar Proposal Name: Mr.Prachya Plasananya ID: 5031305004 Major: Software Engineering Seminar Advisor: Aj. Nikorn Rongbutsri.

Slides:

Advertisements

Similar presentations

Writing a Proposal Sparrow Freshman II. Before starting your research, you should submit a proposal that describes the nature of your research and indicates.

Advertisements

Research skills. OUTLINE Mission and Vision What is Research? Ten Steps for Good Research Resources of Research Types of research Skills (Top_5 Skills)

McGraw-Hill/Irwin © 2006 The McGraw-Hill Companies, Inc. All rights reserved BUSINESS DRIVEN TECHNOLOGY Chapter Nineteen: Building Software to Support.

BUSINESS DRIVEN TECHNOLOGY

Pedigreed Attribute eLicitation Method (PALM) Onno Dijkstra.

U.S. Department of Energy Office of Science Advanced Scientific Computing Research Program How to write a good HBCU Proposal George Seweryniak DOE Program.

Steps, Tools, and Techniques

Banner Reporting “Where O Where Have My Reports Gone?” Presented by Ms. Alma Lynn Bane and Ms. Lauren Morton Tarleton State University February 28, 2007.

Lecture: Requirements Development - Vision and Scope.

1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.

Information Systems Education: What’s missing? Paul H. Rosenthal Information Systems Department, California State University, Los Angeles.

Lab 1 Introduction Project Definition. Introduction and Project definition 2 Objective To give the Student an overview of the Lab Environment and tools.

Objectives Explain the purpose and various phases of the traditional systems development life cycle (SDLC) Explain when to use an adaptive approach to.

Architecture and Requirements

Software Project Management By Assistant Prof. Samana Zehra

What is Business Analysis Planning & Monitoring?

BIS310: Structured Analysis and Design Introduction and Systems Planning Week 1.

S/W Project Management

RUP Fundamentals - Instructor Notes

CpSc 875 John D. McGregor Class 5 – Driving requirements.

Chapter 8: Actor-System Interaction Modeling

Software Requirements The starting point of software development “He kept changing the requirements on us” 1 540f07reqelic4sep4.

6-1 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Chapter 6 Systems Development.

1. Framework project Title of the framework project + claim Background: emblematic picture (this picture is very important: it is the one should illustrate.

Content The system development life cycle

Evaluating Architectural Options Simon Field Chief Technology Officer.

Insert Nonprofit Logo Project Name Discovery Presentation.

The Outline. Introduction Outline 1 Introduction 1.1 Problem Statement –In engineering, a problem is usually in the form of: –Given (some condition) –Subject.

MINI PROJECT GUIDELINES. OBJECTIVE The objective of this mini project is to let the students apply the programming knowledge into a real- world situation/problem.

Architecture Analysis Techniques

Final Year Project 1 (FYP 1)

CpSc 875 John D. McGregor Class 4 – Driving requirements.

University of Southern California Center for Systems and Software Engineering Individual Research Presentation CS 577b Software Engineering II.

Final Year Project 1 (FYP 1) CHAPTER 1 : INTRODUCTION

Requirement engineering & Requirement tasks/Management. 1Prepared By:Jay A.Dave.

Publishing Services Bureau Web Communications Services Tips for managing the publication process Communications Workshop October 23, 2003.

IFS310: Module 2 1/18/2007 Systems Planning and SDLC.

Overview of the Web Development Process.  Website Strategic Plan (Planning)  Content and Site Architecture (Planning)  Website Strawman (Planning)

1. Framework project Title of the framework project + claim Background: emblematic picture (this picture is very important: it is the one should illustrate.

The ATAM method. The ATAM method (1/2) Architecture Tradeoff Analysis Method Requirements for complex software systems Modifiability Performance Security.

Banner Reporting “Where O Where Have My Reports Gone?” Presented by Ms. Alma Lynn Bane and Ms. Lauren Morton Tarleton State University February 28, 2007.

June 7, 2016Action Research and Seminar1 Action Research l The task is NOT finished when the project ends l Participants continue to review, evaluate and.

BSA 385 MASTER Peer Educator/ bsa385master.com FOR MORE CLASSES VISIT

SYSTEM ANALYSIS AND DESIGN LAB NARZU TARANNUM(NAT)

PROPOSED STRATEGIC PLANNING PROCESS DECEMBER 3, 2014 Port of Port Angeles.

1 Statements of Work – Getting Them Right!!. 2 Today’s Agenda A.The Basics B. Sources of Information C. Scenario #1: Procurement is in the loop D. Scenario.

Judy Stafford Comp 190 – Meeting 2 February 2, Working to get it Right.

BSA 385 Entire Course FOR MORE CLASSES VISIT BSA 385 Week 1 DQ 1 BSA 385 Week 1 DQ 2 BSA 385 Week 2 Individual Assignment Frequent.

1 International Institute of Business Analysis Vision: The world's leading association for Business Analysis professionals” Mission: To develop and maintain.

Test Title Test Content.

Title of Project Lead Institution

Process 4 Hours.

Chapter 16: Architecture and Requirements

Title Page Team Name Location.

Title of My Design and Prototype Project

Unified Process (UP).

Name of Author (your name)

Student Name: Student Id: Supervisor’s Name:

Understanding and Planning Business Reports and Proposals

KEY PROCESS AREAS (KPAs)

MANAGING THE DEVELOPMENT AND PURCHASE OF INFORMATION SYSTEMS

Project Lifecycle and IT Product Life Cycle

Training proposal and Reporting

Topic 1: Introduction to the Module and an Overview of Agile

Engine Part ID Part 1.

Engine Part ID Part 2.

Engine Part ID Part 2.

Software Engineering Practices

Final Year Project Structure

Chapter 8: Actor-System Interaction Modeling

Presentation transcript:

Software Engineering Seminar Proposal Name: Mr.Prachya Plasananya ID: Major: Software Engineering Seminar Advisor: Aj. Nikorn Rongbutsri

LOGO Seminar Title Quality Attribute Workshops (QAWs)

LOGO Contents Background and Rational 1 Objective 2 Expected Result 3 Scope 4 Methodology 5 Planning and Duration 6

LOGO Background and Rational  In SDLC analysis and design phase; when design or create system architecture. Sometime may be missing some quality. For this situation has effect to a system to low quality, increase cost or project failure.

LOGO Background and Rational  SEI (Software Engineering Institute) create many technique for solve that problem which QAWs or Quality Attribute Workshops is a one technique for provide important quality attribute and clarify system requirement before create architecture. That gets information from business goal or mission.

LOGO Background and Rational  The result of QAWs includes a list of architecture drivers, the raw scenario, the prioritized list of raw scenario and the refine scenarios.

LOGO Background and Rational  This information can be used to update the organization’s architectural vision, refine system and software requirement, guide the development of prototypes, exercise simulations, understand and clarify the system’s architectural drivers, influence the order in which the architecture is developed, describe the operation of a system and use all information to design the architecture.

LOGO Objective 1)To understand a technique about method to design architecture for gets more quality. Objective 2)Can apply this technique in real life.

LOGO Expected Result  I will understand QAWs a one way technique of SEI for design the architecture and apply this technique to some my project. I will know information and a process of QAWs. I can use QAWs. I know that when use this technique.

LOGO Scope  Information about QAWs  Process of QAWs  QAWs method  Benefit of QAWs

LOGO Methodology  Search a data  Making a proposal  Proposal presentation  Making report project  Presentation preparation and Finish report  Present a project  Submit a final report

LOGO Planning and Duration No. Plan Month JuneJulyAugustSeptemberOctober Search a data 2 Making a proposal 3 Proposal presentation 4 Making report project 5 Presentation preparation and Finish report 6 Present a project 7 Submit a final report