Este documento resume un proyecto de mejoramiento y conservaci坦n vial en el corredor Pisac-Madre de Dios en Per炭. Incluye una inducci坦n general sobre seguridad, salud y medio ambiente, as鱈 como identificaci坦n de peligros, evaluaci坦n de riesgos, permisos requeridos para trabajos de alto riesgo, y reglas de seguridad para el proyecto.
This document discusses improving proto types when using them in collections for RPC applications. It recommends adding an empty message type for void parameters and repeatable types for data collections. Sample code shows defining request/response messages for getting a user by name including a repeated field for the user collection. The server code returns the collection while the client code iterates over it. Implementing an online shop sample is suggested along with using the template method pattern for server internal logic. The document recommends a design patterns book and thanks the reader.
This document provides an overview of software quality assurance and testing. It defines quality as meeting specifications and customer expectations. Software testing investigates quality by providing stakeholders information. Testing is important to prevent defects, as shown by examples of bugs that caused spacecraft and airplane failures costing lives and money. Quality assurance focuses on preventing defects through planning and verification, while quality control identifies defects through action and validation. Defects can be costly so issue tracking systems are used to manage bug lifecycles. Manual testing is time-consuming and relies on human resources while automation testing is faster, more reliable and programmable.
The document discusses different MV* software design patterns - MVC, MVP, and MVVM. It explains the basic structure of each pattern, including how the view, controller/presenter, and model components interact. It provides examples of each pattern, including links to sample applications. The key benefits of these patterns are also summarized, such as separation of concerns, easier testing, and independence of the UI from business logic.
This document discusses best practices for writing clean, readable code. It covers topics like code layout, naming conventions, documentation, code smells, and code reviews. Specifically, it recommends:
- Consistent indentation and ordering for clean layout
- Meaningful naming styles like PascalCase to enhance readability
- Comments to explain difficult code or describe design decisions
- Addressing code smells like long methods or classes that could make code harder to maintain
- Conducting code reviews to improve quality and catch potential bugs
The document discusses the roles and responsibilities of a project manager in software development. It covers the software development lifecycle (SDLC), common methodologies like SCRUM, and the differences between projects and products. It also describes the typical project team roles and the key duties and qualities of an effective project manager, such as planning, organizing, leading, controlling, clear communication, managing expectations, and prioritizing the team over oneself.
This document discusses code quality tools and metrics. It defines technical debt and introduces various metrics like cyclomatic complexity and Chidamber & Kemerer object-oriented metrics to measure code quality. It also discusses tools like SonarQube and SonarLint that can analyze code and provide metrics and reports on code quality, complexity, technical debt and more. SonarQube allows centralizing these metrics and provides different views like code coverage, issues and files. It also features quality gates.
This document discusses design patterns, which are general and reusable solutions to common problems in software design. It covers three categories of design patterns: creational patterns, structural patterns, and behavioral patterns. The document also lists some common antipatterns to avoid, such as singleton patterns, spaghetti code, and magic numbers. It recommends some online resources for learning more about design patterns with examples and explanations of when to use specific patterns.
Integration tests test multiple components together by using dependencies like databases, services, and APIs. They are useful for testing typical workflows and ensuring components interact smoothly but can be hard to write, maintain, and localize errors. UI tests with Selenium automate interactions with a web application like users do in order to detect errors not found by other test types, but take more time and setup compared to unit tests.
The document provides an overview of communication capabilities in Android, including networking, useful networking libraries, Bluetooth, and Near Field Communication (NFC). It discusses how to connect to networks, perform network operations on a separate thread, check network connectivity, download data using HTTPURLConnection, and efficiently manage network usage. Libraries covered include Retrofit, okHTTP, Volley, and RoboSpice. The document also provides examples of discovering Bluetooth devices, connecting to Bluetooth devices, and implementing Bluetooth profiles. It concludes with a brief description of NFC technology.
This document provides an overview of software quality assurance and testing. It defines quality as meeting specifications and customer expectations. Software testing investigates quality by providing stakeholders information. Testing is important to prevent defects, as shown by examples of bugs that caused spacecraft and airplane failures costing lives and money. Quality assurance focuses on preventing defects through planning and verification, while quality control identifies defects through action and validation. Defects can be costly so issue tracking systems are used to manage bug lifecycles. Manual testing is time-consuming and relies on human resources while automation testing is faster, more reliable and programmable.
The document discusses different MV* software design patterns - MVC, MVP, and MVVM. It explains the basic structure of each pattern, including how the view, controller/presenter, and model components interact. It provides examples of each pattern, including links to sample applications. The key benefits of these patterns are also summarized, such as separation of concerns, easier testing, and independence of the UI from business logic.
This document discusses best practices for writing clean, readable code. It covers topics like code layout, naming conventions, documentation, code smells, and code reviews. Specifically, it recommends:
- Consistent indentation and ordering for clean layout
- Meaningful naming styles like PascalCase to enhance readability
- Comments to explain difficult code or describe design decisions
- Addressing code smells like long methods or classes that could make code harder to maintain
- Conducting code reviews to improve quality and catch potential bugs
The document discusses the roles and responsibilities of a project manager in software development. It covers the software development lifecycle (SDLC), common methodologies like SCRUM, and the differences between projects and products. It also describes the typical project team roles and the key duties and qualities of an effective project manager, such as planning, organizing, leading, controlling, clear communication, managing expectations, and prioritizing the team over oneself.
This document discusses code quality tools and metrics. It defines technical debt and introduces various metrics like cyclomatic complexity and Chidamber & Kemerer object-oriented metrics to measure code quality. It also discusses tools like SonarQube and SonarLint that can analyze code and provide metrics and reports on code quality, complexity, technical debt and more. SonarQube allows centralizing these metrics and provides different views like code coverage, issues and files. It also features quality gates.
This document discusses design patterns, which are general and reusable solutions to common problems in software design. It covers three categories of design patterns: creational patterns, structural patterns, and behavioral patterns. The document also lists some common antipatterns to avoid, such as singleton patterns, spaghetti code, and magic numbers. It recommends some online resources for learning more about design patterns with examples and explanations of when to use specific patterns.
Integration tests test multiple components together by using dependencies like databases, services, and APIs. They are useful for testing typical workflows and ensuring components interact smoothly but can be hard to write, maintain, and localize errors. UI tests with Selenium automate interactions with a web application like users do in order to detect errors not found by other test types, but take more time and setup compared to unit tests.
The document provides an overview of communication capabilities in Android, including networking, useful networking libraries, Bluetooth, and Near Field Communication (NFC). It discusses how to connect to networks, perform network operations on a separate thread, check network connectivity, download data using HTTPURLConnection, and efficiently manage network usage. Libraries covered include Retrofit, okHTTP, Volley, and RoboSpice. The document also provides examples of discovering Bluetooth devices, connecting to Bluetooth devices, and implementing Bluetooth profiles. It concludes with a brief description of NFC technology.
This document provides an overview of best practices for Android Wear development. It discusses how to pair Wear devices, common APIs with Android, showing notifications, distributing Wear apps, defining layouts, accessing views, useful libraries like Gson and EventBus, and other tips.
The document provides an overview of Android application development fundamentals including application components, intents, manifest files, and more. It discusses that Android apps are written in Java and compiled to APK files. The core application components are activities, services, broadcast receivers, and content providers. Intents are used to start components and broadcast receivers register to receive system or app events. Every app must declare its components in the Android manifest.
The document discusses Android location and sensor APIs. It provides an overview of location services in Android, which allows apps to access location through the LocationManager. It also discusses the sensors framework, which gives access to motion, position, and environment sensors. It describes how to identify available sensors, register listeners to receive sensor events, and handle the sensor data. Key classes like SensorManager, Sensor, and SensorEventListener are also summarized.
This document provides an introduction to the Java programming language. It discusses the goals of Java, including being cross-platform, providing security through sandboxing with the Java Virtual Machine, and replacing C/C++. It explains what is needed to run and develop Java applications and the differences between Java editions. The document outlines some key differences between Java and C#/C++ and how to write a basic Java application. It also defines JAR files and provides principles for designing class structures in Java.
This document provides instructions for creating a gRPC Hello World sample in C# using .NET Core. It describes creating client and server projects with protobuf definition files. The server project implements a Greeter service that returns a greeting message. The client project calls the SayHello method to get a response from the server. Running the projects demonstrates a basic gRPC communication.
DevOps is a culture and practice that aims to rapidly build, test, and release software. Continuous integration requires developers to integrate code into a shared repository multiple times a day, with each check-in verified by automated builds to detect problems early. Continuous delivery is the practice of releasing every good build to users. Popular tools for continuous integration include TeamCity, Jenkins, and others.
The document discusses the role of a user experience designer, outlining their design process which includes discovering user requirements, creating design concepts and prototypes, validating designs through research and testing, and iterating on their work through collaboration and learning. It emphasizes the importance of an iterative design process driven by user needs.
The document discusses the role of a business analyst in a software project. It explains that a business analyst is involved in requirements gathering and representation. This includes eliciting requirements through preliminary discussions with customers, reviewing requirements with other roles like architects and UX designers, and specifying requirements. Requirements can be represented through user stories, use cases, documents, and other methods. User stories are written from the perspective of users and define what they want to do. Use cases outline interactions between actors and a system. Together, clearly documented requirements help ensure a project delivers business value through the right software solution.
37. Example
public static class StringExtension
{
public static int WordCount(this string str, char c)
{
int counter = 0;
for (int i = 0; i<str.Length; i++)
{
if (str[i] == c)
counter++;
}
return counter;
}
}
int i = s.WordCount(c);
40. OthersC# VB.NET
.NET Language Integrated Query (LINQ)
LINQ
to SQL
LINQ
to Objects
LINQ
to XML
LINQ
to Datasets
LINQ
to Entities
LINQ data source providers
ADO.NET support for LINQ
41. 舒亶仗仂亠 于亳亰仆舒亠仆仆 亰舒仗亳舒 LINQ
from 亰仄仆仆舒 in 仆舒弍-仂弍从于
select 亰仄仆仆舒;
舒仗亳亳 LINQ
42. 弍从亳 于亳从仂亳仂于ﾑ 亳从仍亳 仄仂于亳
foreach(Customer c in customers) if (c.Region == "UK") ...
舒亰亳 亟舒仆亳 于亳从仂亳仂于ﾑ SQL
SELECT * FROM Customers WHERE Region='UK'
XML 于亳从仂亳仂于 XPath/XQuery
//Customers/Customer[@Region='UK']
舒仗亳亳 弍亠亰 LINQ
43. 舒仗亳亳 亰 LINQ
var myCustomers = from c in customers
where c.Region == "UK"
select c;
var goodCusts = (from c in db.Customers
where c.PostCode.StartsWith("GY")
orderby c.Sales descending
select c).Skip(10).Take(10);
45. 仄 舒仆亟舒仆仂亞仂 亳仆舒从亳 from .. in .. select 亟仍 于仂亠仆仆 亰舒仗亳
LINQ 仄亳 仄仂亢亠仄仂 亰舒仂仂于于舒亳 仗亠舒仍仆 仄亠仂亟亳 仂亰亳亠仆仆, 磻
于亳亰仆舒亠仆 于 仆亠亠亶 IEnumerable.
亠 从仂亢亠仆 仄亠仂亟 仂亰亳亠仆仆 仄舒 舒仆舒仍仂亞 亠亠亟 仂仗亠舒仂于 LINQ, 于
仂仄 于亳仗舒亟从 仄仂亢仆舒 亰舒仂仂于于舒亳 仂弍亳亟于舒 仗亟仂亟亳.
string[] teams = { "舒于舒", "仂", "亠舒仍 舒亟亳亟", "舒仆亠亠 弌", "舒亠仍仂仆舒" };
int number = (from t in teams where t.ToUpper().StartsWith("") select t).Count();
亠仂亟亳 仂亰亳亠仆仆 LINQ
46. var contacts =
from c in customers
where c.City == "Hove"
select new { c.Name, c.Phone };
var contacts =
customers
.Where(c => c.City == "Hove")
.Select(c => new { c.Name, c.Phone });
Extension
methods
Lambda
expressions
Query expressions
Object initializersAnonymous
types
Local variable type
inference
49. 亠从仂仄亠仆亟仂于舒仆舒 仍亠舒舒
1. R. Sedgewick Algorithms
2. A. Troelsen C# 6.0 and the .NET 4.6 Framework
3. H. Schildt C# 4.0 The Complete Reference
4. J. Richter CLR via C#
5. J. Skeet C# in Depth
6. Stackoverflow.com
![Example
public static class StringExtension
{
public static int WordCount(this string str, char c)
{
int counter = 0;
for (int i = 0; i<str.Length; i++)
{
if (str[i] == c)
counter++;
}
return counter;
}
}
int i = s.WordCount(c);](https://image.slidesharecdn.com/advancedcsharppart2-160324091819/85/Advanced-C-Part-2-37-320.jpg)
![弍从亳 于亳从仂亳仂于ﾑ 亳从仍亳 仄仂于亳
foreach(Customer c in customers) if (c.Region == "UK") ...
舒亰亳 亟舒仆亳 于亳从仂亳仂于ﾑ SQL
SELECT * FROM Customers WHERE Region='UK'
XML 于亳从仂亳仂于 XPath/XQuery
//Customers/Customer[@Region='UK']
舒仗亳亳 弍亠亰 LINQ](https://image.slidesharecdn.com/advancedcsharppart2-160324091819/85/Advanced-C-Part-2-42-320.jpg)
![仄 舒仆亟舒仆仂亞仂 亳仆舒从亳 from .. in .. select 亟仍 于仂亠仆仆 亰舒仗亳
LINQ 仄亳 仄仂亢亠仄仂 亰舒仂仂于于舒亳 仗亠舒仍仆 仄亠仂亟亳 仂亰亳亠仆仆, 磻
于亳亰仆舒亠仆 于 仆亠亠亶 IEnumerable.
亠 从仂亢亠仆 仄亠仂亟 仂亰亳亠仆仆 仄舒 舒仆舒仍仂亞 亠亠亟 仂仗亠舒仂于 LINQ, 于
仂仄 于亳仗舒亟从 仄仂亢仆舒 亰舒仂仂于于舒亳 仂弍亳亟于舒 仗亟仂亟亳.
string[] teams = { "舒于舒", "仂", "亠舒仍 舒亟亳亟", "舒仆亠亠 弌", "舒亠仍仂仆舒" };
int number = (from t in teams where t.ToUpper().StartsWith("") select t).Count();
亠仂亟亳 仂亰亳亠仆仆 LINQ](https://image.slidesharecdn.com/advancedcsharppart2-160324091819/85/Advanced-C-Part-2-45-320.jpg)
