•  

Our Top Course
Komunikasi Pembelajaran
( 16 Sections)
 
Pengembangan Media Foto
( 16 Sections)
 

Course Analisis dan Desain sistem

Program Studi S1 Bisnis Digital UNESA

 
Card image

Deskripsi Mata Kuliah

Salah satu tahapan yang krusial dalam pengembangan perangkat lunak ialah rekayasa kebutuhan. Kesuksesan proyek pengembangan perangkat lunak dicapai ketika kebutuhan stakeholder dapat terpenuhi sesuai apa yang dijanjikan oleh pengembang. Maka dalam proses awal pengembangan perangkat lunak, mahasiswa perlu pemahaman mengenai rekayasa sistem dan perangkat lunak, metode dalam menggali kebutuhan stakeholder, teknik dalam menganalisis, dan pendekatan dalam mendokumentasikan spesifikasi kebutuhan perangkat lunak. Kegiatan dalam perkuliahan ini akan dilakukan dengan metode pembelajaran mandiri dan berkelompok agar dapat melatih mahasiswa ketika nantinya terlibat langsung dalam proyek pengembangan perangkat lunak. (One of the crucial stages in software development is requirements engineering. The success of a software development project is achieved when stakeholder needs can be fulfilled according to what was promised by the developer. So, in the initial process of software development, students need an understanding of system and software engineering, methods for exploring stakeholder needs, techniques for analyzing, and approaches for documenting software requirements specifications. Activities in this lecture will be carried out using independent and group learning methods so that they can train students when they are directly involved in software development projects.)

CPMK

  • Mahasiswa mampu menjelaskan spesifikasi kebutuhan perangkat lunak [C2, A2] | Students are able to explain software requirement specification [C2, A2]
  • Mahasiswa mampu mendefinisikan kebutuhan tingkat tinggi dan kandidat domain [C3, A2] | Students are able to define high-level requirement and domain candidate [C2, A2]
  • Mahasiswa mampu menganalisis dan mengelisitasi spesifikasi kebutuhan perangkat lunak [C3, P2, A2] | Students are able to analyze and to elicit software requirement specification [C3, P2, A2]
  • Mahasiswa mampu membuat rancangan diagram unified modelling language (UML) sesuai kebutuhan perangkat lunak [C4, P3, A2] | Students are capable to design software specification using UML diagram [C4, P3, A2]

Aktifitas Pembelajaran

  • Pertemuan 1
    Konsep analisis kebutuhan perangkat lunak berbasis kerangka kerja [C2, A2] | Students are able to understand concept of software requirement analysis using framework [C2, A2]
    • Date  9 Februari 2024

  • Pertemuan 2
    Konsep analisis kebutuhan perangkat lunak berbasis kerangka kerja [C2, A2] | Students are able to understand concept of software requirement analysis using framework [C2, A2]
    • Date  16 Februari 2024

  • Pertemuan 3
    Kebutuhan sistem tingkat tinggi dan objek domain [C3, A2] | Students are able to define a high-level requirement system and domain objects [C3, A2]
    • Date  23 Februari 2024

  • Pertemuan 4
    Menganalisis kebutuhan fungsional dan non-fungsional berdasarkan cerita pengguna [C3, A2] | Students are able to analyze functional and non-functional requirement based on user stories [C3, A2]
    • Date  1 Maret 2024

  • Pertemuan 5
    Menganalisis kebutuhan fungsional dan non-fungsional berdasarkan cerita pengguna [C3, A2] | Students are able to analyze functional and non-functional requirement based on user stories [C3, A2]
    • Date  8 Maret 2024

  • Pertemuan 6
    Menyusun scenario/ narasi kasus penggunaan dari kebutuhan fungsional sistem [C3, A2, P2] | Students are able to compose use case narratives based on functional requirement system [C3, A2, P2]
    • Date  15 Maret 2024

  • Pertemuan 7
    Menyusun scenario/ narasi kasus penggunaan dari kebutuhan fungsional sistem [C3, A2, P2] | Students are able to compose use case narratives based on functional requirement system [C3, A2, P2]
    • Date  22 Maret 2024

  • Pertemuan 8
    Mempresentasikan keterkaitan antara high-level requirement, kebutuhan fungsional, hingga narasi use case dengan komprehensif [C3, P2, A3] Students are able to present the correlation between highlevel requirement, functional requirements, to use case narratives comprehensively [C3, P2, A3]
    • Date  29 Maret 2024

  • Pertemuan 9
    Membuat desain sistem menggunakan diagram UML seperti Use Case Diagram, Sequence Diagram, dan Activity Diagram [C4, P2, A2] | Students are able to create UML diagram such use case diagrams, sequence diagrams, and activity diagrams [C4, P2, A2]
    • Date  5 April 2024

  • Pertemuan 10
    Membuat desain sistem menggunakan diagram UML seperti Use Case Diagram, Sequence Diagram, dan Activity Diagram [C4, P2, A2] | Students are able to create UML diagram such use case diagrams, sequence diagrams, and activity diagrams [C4, P2, A2]
    • Date  12 April 2024

  • Pertemuan 11
    Membuat desain sistem menggunakan diagram UML seperti Use Case Diagram, Sequence Diagram, dan Activity Diagram [C4, P2, A2] | Students are able to create UML diagram such use case diagrams, sequence diagrams, and activity diagrams [C4, P2, A2]
    • Date  19 April 2024

  • Pertemuan 12
    Membuat analisis dan desain sistem berdasarkan ide bisnis secara kohesif dan komprehensif [C4, P3, A2] | Students are able to create system analysis and design based on business idea cohesively and comprehensively [C4, P3, A2]
    • Date  26 April 2024

  • Pertemuan 13
    Membuat analisis dan desain sistem berdasarkan ide bisnis secara kohesif dan komprehensif [C4, P3, A2] | Students are able to create system analysis and design based on business idea cohesively and comprehensively [C4, P3, A2]
    • Date  3 Mei 2024

  • Pertemuan 14
    Membuat analisis dan desain sistem berdasarkan ide bisnis secara kohesif dan komprehensif [C4, P3, A2] | Students are able to create system analysis and design based on business idea cohesively and comprehensively [C4, P3, A2]
    • Date  10 Mei 2024

  • Pertemuan 15
    Membuat analisis dan desain sistem berdasarkan ide bisnis secara kohesif dan komprehensif [C4, P3, A2] | Students are able to create system analysis and design based on business idea cohesively and comprehensively [C4, P3, A2]
    • Date  17 Mei 2024

  • Pertemuan 16
    Mempresentasikan dokumen konsep operasi yang utuh suatu ide sistem bisnis digital berdasarkan framework tertentu [C4, A3, P3] | Students are capable to present the IEEE Concept of operations document properly [C4, A3, P3]
    • Date  24 Mei 2024

Dosen

RENNY SARI DEWI
RENNY SARI DEWI
  • 215,475 Reviews4.8 Rating

RISKA DHENABAYU
RISKA DHENABAYU
  • 215,475 Reviews4.8 Rating

Video Images
Preview this course
 
 
  • Program StudiS1 Bisnis Digital
  • Semester4
  • Lectures2
Difficult Things About Education.
$75$10