پاورپوینت کامل CSEB233 Fundamentals of Software Engineering 53 اسلاید در PowerPoint

توجه : این فایل به صورت فایل power point (پاور پوینت) ارائه میگردد

 پاورپوینت کامل CSEB233 Fundamentals of Software Engineering 53 اسلاید در PowerPoint دارای ۵۳ اسلاید می باشد و دارای تنظیمات کامل در PowerPoint می باشد و آماده ارائه یا چاپ است

شما با استفاده ازاین پاورپوینت میتوانید یک ارائه بسیارعالی و با شکوهی داشته باشید و همه حاضرین با اشتیاق به مطالب شما گوش خواهند داد.

لطفا نگران مطالب داخل پاورپوینت نباشید، مطالب داخل اسلاید ها بسیار ساده و قابل درک برای شما می باشد، ما عالی بودن این فایل رو تضمین می کنیم.

توجه : در صورت  مشاهده  بهم ریختگی احتمالی در متون زیر ،دلیل ان کپی کردن این مطالب از داخل فایل می باشد و در فایل اصلی پاورپوینت کامل CSEB233 Fundamentals of Software Engineering 53 اسلاید در PowerPoint،به هیچ وجه بهم ریختگی وجود ندارد

بخشی از مطالب داخلی اسلاید ها

پاورپوینت کامل CSEB233 Fundamentals of Software Engineering 53 اسلاید در PowerPoint

اسلاید ۴: Analysis Models Design ModelThe four design models: Each of the elements of the analysis/requirements model provides information that is necessary to create the design models required for a complete design specification.Badariah Solemon 2011

اسلاید ۵: Characteristics of Good DesignAccording to McGlaughlin(1991):Must implement all of the explicit requirements contained in the analysis model, and it must accommodate all of the implicit requirements desired by the customer.Must be a readable, understandable guide for those who generate code and for those who test and subsequently support the software.Should provide a complete picture of the software, addressing the data, functional, and behavioral domains from an implementation perspective.Badariah Solemon 2011

اسلاید ۶: Design PrinciplesAccording Davis(1995 ):The design process should not suffer from ‘tunnel vision.’ The design should be traceable to the analysis model. The design should not reinvent the wheel. The design should “minimize the intellectual distance” [DAV95] between the software and the problem as it exists in the real world. The design should exhibit uniformity and integration. Badariah Solemon 2011

اسلاید ۷: Design Principle: Badariah Solemon 2011The design process should not suffer from ‘tunnel vision.’The design should not reinvent the wheel.Reinventing the wheel is a phrase that means to duplicate a basic method that has already previously been created or optimized by others.

اسلاید ۸: Design Principles (cnt’d)The design should be structured to accommodate change. The design should be structured to degrade gently, even when irregular data, events, or operating conditions are encountered. Design is not coding, coding is not design. The design should be assessed for quality as it is being created, not after the fact. The design should be reviewed to minimize conceptual (semantic) errors.Badariah Solemon 2011

اسلاید ۹: Generic Task Set for DesignRefer to the “Task Set” in page 222.Badariah Solemon 2011

اسلاید ۱۰: Design ConceptsFundamental design concepts that span both traditional and OO software development include:Abstraction ArchitecturePatternsSeparation of concernsModularityInformation hidingFunctional IndependenceRefinementAspectsRefactoringOO Design conceptsDesign classesBadariah Solemon 2011

اسلاید ۱۱: AbstractionDesigners should work to derive both procedural and data abstractions that serve the problem.Procedural abstraction – sequence of instructions that have a specific and limited functionData abstractions – a named collection of data that describes a data objectBadariah Solemon 2011

اسلاید ۱۲: Abstraction (cnt’d)Badariah Solemon 2011door manufacturer model number type swing direction weightimplemented as a data structuredoordetails of enter algorithmimplemented with a knowledge of the object that is associated with “enter”

اسلاید ۱۳: Abstraction (cnt’d)Data abstraction refers to, providing only essential features by hiding its background details. class result{int marks;float percentage;char name[20];void input();void output();} main(){bank b1;b1.input();b1.output();}b1 is an object calling input and output member functions, but that code is invisible to the object b1.Badariah Solemon 2011

اسلاید ۱۴: Architecture Is concerned on:describing the fundamental organization of the system, identifying its various components and their relationships to each other, and the environment in order to meet the systems quality goals.Also, describe the overall structure of the software : organization of program modules, the manner in which these modules interact, and the structure of data used by the components.Badariah Solemon 2011

اسلاید ۱۵: PatternsOnline pattern searching:http://inventor/gi/dynamic/offsite.htmsite=http%3A%2F%Fpatents.uspto.gov%2Fpatft%2Findex.html Under Quick Search, try to search pattern no. 7669112.You will get ‘automated spell analysis’ pattern.Badariah Solemon 2011

اسلاید ۱۶: Separation of ConcernsActually, it is a rule of thumb to define how modules should be separated to each other: different or unrelated concerns should be restricted to different modules.Suggests that any complex problem can be easily handled if it is sub-divided into pieces that can be solved independently. Why So that a problem takes less time and effort to solve.Is manifested in other design concepts: modularity, aspects, functional independence and refinement.Badariah Solemon 2011

اسلاید ۱۷: ModularityWhen software is divided into components (modules).Modularize a design: To ease the planning for implementation (coding, To define and deliver software increments,To easily accommodate changes,To efficiently test and debug program, andTo conduct long-term maintenance without serious side effects Badariah Solemon 2011

اسلاید ۱۸: Modularity : ExamplexBadariah Solemon 2011#include <stdio.h>main() { …printf(“This program draws a rectangle”);…}#include <stdio.h>void print_menu(void);main() { …print_menu();…} /* end main */void print_menu(void) {printf(“This program draws a rectangle”);} /* end f